On 5/5/05, Troy Rollo wine@troy.rollo.name wrote:
Precisely. WINE is not just for running apps compiled for Windows - it's also for making the Windows API available under UNIX. For this second application, users need to (at a minimum) be seeing UNIX paths (and not Windows paths at all) in the dialog. It is also reasonable in this context for the application to expect to use APIs with UNIX paths without having to convert them.
wine wasn't designed to accept unix paths in the apis directly or to display them in open file dialogs, and that's why we have virtual drives.
I'm leaning toward the separate entry point solution (the various approaches were canvassed here a couple of weeks ago) since it avoids problems with Microsoft adding new flags of their own later that use the same values as WINE specific flags.
This just adds complexity to an already complex beast. Keep it simple.