Hi,
We are using GetFileSaveName to get file store to disk.
As this is a Windows session it get its one windows session an is not listed as an prosess under our MDI.
When running program that use some time before asking for the filename, then the result is that users may do other tings while waiting and they don't see this process waiting for their input as user pay attetion to the MDI session.
Is there any possibility getting this fileprosess to be a prosess under our mdi ? Or do we had to make our one window asking for filename in situations like this?
regards
Ivan
I agree 100% the GetFileSaveName method opens a Response (modal) window in the same thread (process) as the PB App. That means that the O/S dialogue is "in the users" face at all times and the MDI window cannot get control (aka Focus) back until it closes.
Regards ... Chris
I do not disagree on that it is a modal window, but its seems like it in some cases also shown with it's own processe icon on Windows processline. Sp I think I will try the multi-threaded proposal from Chris.
Ivan
A little clarification.
What we see when it becomes to this "own process" is that you get "getfileSaveName" as own "process" when using Alt+tab in windows.
So Customers experiences this as a separate process that does not show up if one choose the MDI window from this Alt-Tab view. Although "getfilesave" is a modal window beneath then MDI process.
When Customer choose "GetFileSaveName" window it all work fine.
Regards
Ivan.