Then it should not be a Dialog but a form that you can decide when to hide / destroy it ?
Isn't that just a matter of semantics?
I don't think that a dialog needs to be modal, just in order to call it a dialog.
If you have Delphi execute a finddialog (or do a find in MS Word or OpenOffice.org) and a non-modal find or replace form appears, which I tend to call a dialog. This is what I'm after.
If you show the Save Dialog then user must first finish saving before continuing.
The FileOpen dialog's purpose is to let the user make one (and only one) choice, only one time (we do not want the user to press "save" and after that "cancel", that would not make sense would it). So in this case make it modal and check modalresult to see what the user wants.
A find/replace dialog however gives the user the possibility to find text, alter it if he wants, find next occurence, change direction in finding etc.
I find this feature rather helpull and so do many other end-users.
Since I make most of my software for either myself, or for almost computer-illetarates, I tend to give the user what he/she expects.
In the Windows environment that is the behaviour I described above.
But I'm repeating myself and my arguments.
... (ShowSearchReplace(aSynEdit:TSynEdit)
SynMemo1.ShowSearchReplace;utest.pas(159,12) Error: identifier idents no member "ShowSearchReplace"
Let's agree that we can disagree on wether or not we want a non-modal dialog.
Say I want a non-modal dialog/form that stay's on top of all windows from it's own application, but not on top of all windows on the desktop.
Does anyone have any idea as how to achieve this, OS/WindowManager independently?
Bart