kbad@atari.UUCP (Ken Badertscher) (07/04/89)
to_stdnet@stag.UUCP writes: | From: stag!thelake!steve@bungia.mn.org (Steve Yelvington) | 89Jun24 9:37 pm from Ian@The Vale (We have returned!) | [...] | About that Usenet message from Ken B. concerning AC_CLOSED messages and | freeing up memory/file handles from within an accessory... I did a little | playing with the concept recently, and it seems like you get the AC_CLOSED | message **after** then main application has been Pterm'd by DOS. Desk accessories get AC_CLOSED messages when an application calls appl_exit. That's the only time the AES sends AC_CLOSED messages. Of course, if an application has already terminated, it can hardly be calling appl_exit ;-). The desktop itself also calls appl_exit on a resolution change and just before* an application is launched (to tell the AES that it is exiting). The AC_CLOSED messages that the desktop sends to accessories don't mean that they're going to lose anything, because the desktop never really terminates as such (except on a resolution change). | Speaking of GEM and DRI docs... Here's one for you: During form_do() | (dialog) processing, if the user double-clicks on an object defined as | TOUCHEXIT, the object index of the exit object as returned from form_do() has | the high bit set. Yup. If you don't care about double click reporting, always lop off the high bit of the return from form_do before using it as an object index! -- ||| Ken Badertscher (ames!atari!kbad) ||| Atari R&D System Software Engine / | \ #include <disclaimer>
kbad@atari.UUCP (Ken Badertscher) (07/04/89)
to_stdnet@stag.UUCP writes: | From: stag!thelake!steve@bungia.mn.org (Steve Yelvington) | 89Jun24 9:37 pm from Ian@The Vale (We have returned!) | [...] | About that Usenet message from Ken B. concerning AC_CLOSED messages and | freeing up memory/file handles from within an accessory... I did a little | playing with the concept recently, and it seems like you get the AC_CLOSED | message **after** then main application has been Pterm'd by DOS. Desk accessories get AC_CLOSED messages when an application calls appl_exit. That's the only time the AES sends AC_CLOSED messages. Of course, if an application has already terminated, it can hardly be calling appl_exit ;-). The desktop itself also calls appl_exit on a resolution change and just before* an application is launched (to tell the AES that it is exiting). The AC_CLOSED messages that the desktop sends to accessories don't mean that they're going to lose anything, because the desktop never really terminates as such (except on a resolution change). | Speaking of GEM and DRI docs... Here's one for you: During form_do() | (dialog) processing, if the user double-clicks on an object defined as | TOUCHEXIT, the object index of the exit object as returned from form_do() has | the high bit set. Yup. If you don't care about double click reporting, always lop off the high bit of the return from form_do before using it as an object index! -- ||| Ken Badertscher (ames!atari!kbad) ||| Atari R&D System Software Engine / | \ #include <disclaimer>