On Tue, 4 Jan 2005, Dimitrie O. Paun wrote: [...]
- How paths are presented to the app This is something that needs to be per app. One way to do it would be to follow Miscrosoft and ornate apps somehow (the same they do for themable apps) via some sort of manifest that would request Unix paths instead of DOS ones. Same mechanism could be used for other things, like requesting native open dialogs instead of ours, etc.
Shouldn't this be a per-call thing rather than a per-app thing?
An application may be built from multiple components, some of which may not support being given a Unix path. Here are two scenarios where this might be an issue: * COM embedding A Unix path aware app embeds a COM component which presents a dialog to the user for some reason. IF the flag is app-global the COM component will get a Unix path and be confused.
* An application supporting plugins It's a similar issue: that the app supports Unix paths does not mean that all its plugins support them. For instance a Winelib web browser that would load an HTML page that uses an ActiveX component to display a PDF file. That ActiveX component may have a button that lets the user save the PDF file. This button would open a dialog and if that dialog uses the application's global flag it would return a Unix path.
The short of it is that only the code invoking the common dialog knows whether it is prepared to deal with Unix paths or not and thus is the only one who can say whether the dialog should return Unix paths.