The FileSel::Set() does not appear to work correctly as of 2008.1beta if FileSel::ExecuteOpen() is used. The directory is correctly set, but the requested filename does not end up in the file field. FileSel::Set() works as expected though when FileSel::ExecuteSaveAs() is used.
It would be of great benefit in certain applications to have it work in normal Open... situations too. Imagine a user of an application program manually working through a set of cryptically named files in alphabetical order... OK, having the previously processed file pre-selected in the dialog when opening the next would help quite a bit.
(The windows platform file dialog does this.)
Unfortunately, I could not see to the depths required to make this work in FileSel code.
dolik.rce Messages: 1781 Registered: August 2008 Location: Czech Republic
I'm sorry for unclear formulation, SaveAs always worked perfectly. What I meant to say was that it would help when opening files differing only in suffixes.
One more example where I would use preselected filename came to my mind: Suppose I have an application which handles some data file and configuration file telling it what to do with those data. Now if user already opened configuration file, it would be a nice feature to preselect a corresponding file when opening the data. (For example based on filename of configuration file - perhaps with a check that it exist).
Idea with Preselect field sounds good to me. If you could implement it I would really aprreciate it. Just hope it's not too much work, I wouldn't want to distract you from more important things