Quote:
Originally Posted by videoFred
Why not? It makes changing filter parameter values so easy...  |
Well I guess I'm just awkward.
I dont like the way it changes my scripts, and eg inserts filenames in scripts that I use with eg FSelOpen, ie breaks my scripts.
Code:
RT_FSelOpen(string "title"="Open",string "dir"="",string "filt",string "fn="",bool "multi"=false,bool "debug"=false)
Function to select EXISTING filename using GUI FileSelector.
Title = Title bar text.
Dir = Directory, "" = Current
Filt = Lots, eg "All Files (*.*)|*.*"
[Displayed text | wildcard] [| more pairs of Displayed text and wildcard, in pairs ONLY].
first one is default.
fn = Initially presented filename (if any).
multi = Multiply Select filenames. Allows selection of more than one filename at once.
debug = Send error info to DebugView window.
Returns
int, 0, user CANCELLED.
int, non zero is error (error sent to DebugView window).
String, Filename selected, Chr(10) separated multiline string if MULTI==true (and multiple files selected).
Example, to prompt for an AVI file and play it.
avi=RT_FSelOpen("I MUST have an AVI",filt="Avi files|*.avi")
Assert(avi.IsString,"RT_FSelOpen: Error="+String(avi))
AviSource(avi)
I do have it installed, but rarely use it (not in last 12 months probably). Having said that, I used AVSEdit up until about 18 months ago and I hated it, as said, I'm a bit awkward.
