Re: Extending File Dialog to include unix file paths [4/4]

2005-05-15 Thread Michael Lin
Hi Michael, Our work on this topic basically have the same goal but slightly different approach. We both want to extend the file dialog to include unix file path without changing the current behaviour for current user if they don't want unix file path. I believe our patchs should be merged to

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-13 Thread Steven Edwards
Hi, --- Francois Gouget <[EMAIL PROTECTED]> wrote: > No, that should not happen. If an application links with a library that > exports funcA() and funcB() but it only calls funcA(), then it will only > import funcA() and it will work on a system where that library only > exports funcA(). OK ma

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-13 Thread Francois Gouget
On Thu, 12 May 2005, Steven Edwards wrote: [...] But your defining UnixFSGetOpenFileNameW in the spec file so the import library will still have that function listed so if I link a dll to that import library its going to fail on Windows even if I am not calling that function. No, that should not

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-13 Thread Michael Jung
Hi all, please find attached my current work on this topic. It takes another approach as Michael Lin's patches and in particular doesn't add any API. I've already send the smaller of the two patches to wine-patches, so it may well be that this one is already applied when you try the patches. T

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-12 Thread Steven Edwards
Hi Michael, --- Michael Lin <[EMAIL PROTECTED]> wrote: > If your target platform is windows, don't define the WINE_UNIX_PATHS > flag when you compile and it will all behave > the same as before. It's only when you define WINE_UNIX_PATHS flag that > GetOpenFileNameW() will be mapped > to UnixFSGe

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-12 Thread Michael Lin
Hi Steve, Steven Edwards wrote: --- Michael Lin <[EMAIL PROTECTED]> wrote: --- dlls/commdlg/comdlg32.spec +@ stdcall UnixFSGetOpenFileNameA(ptr) +@ stdcall UnixFSGetOpenFileN Is there anyway for us to have these functions inlined or something rather than exported all the time is there? The reason

Re: Extending File Dialog to include unix file paths [4/4]

2005-05-12 Thread Steven Edwards
Hi Michael, I really like the idea of trying to tie the apps in better for users of Winelib applications but I have a few problems. (I should have spoken up when the first of the Unixfs stuff was going in to shell32 because I feel it should have been a shellext outsite of shell32 but now I am o