>> now, if someone could explain to me why a SDI application sometimes not
>> stops its process after exiting...
>
>You have probably allowed the last window to close without quitting the app.
>On the Mac this will leave you with no open windows but a visible menubar.
>On an SDI app the menu disappears when the window closes. You may be able
>to solve it for your app by quitting in the window close event.
thank you for the tip. in fact, in an SDI app i cannot really control if
the user closes the window on the right side or on the left side of with
quit. so adding quit in the close event will fix it.
i am already on another question with win32 SDI. the tutorial proposes to
relaunch the application as an answer to the filenew menu. it does
however not talk about the fileopen menu. if the file extension is not
associated with the application, i cannot launch the document. can i
launch the application telling it to launch a document? (possible
workaround would be to write to an .ini file before launching which has a
path to the file to be opened)
or if open within the document, i will make disappear the existing
document, so if this is not saved, i should ask to save before? wouldn't
be too elegant to ask to save before getting the open dialog, would it?
or is the SDI just a no-no for document oriented applications?
matthias
-----------------------------------------------------
matthias buercher belle nuit montage fax 4112742114
matti at belle-nuit dot com http://www.belle-nuit.com
-----------------------------------------------------
|