hello! The mac (lw 4.3.6) version of my capi program often hangs if it tries to do a (lw:quit) - is there any caveats I'm not aware of? A related question: How do I know that the user has requested my application to quit through the standard Quit menu item? -- (espen)
Unable to parse email body. Email id is 1357
(answering a little late, I was on holiday) David Fox <davef@xanalys.com> writes: > It looks like there are problems if the GUI thread calls QUIT. > > We're going to look into that, but in the meantime a workaround might > be to use MP:PROCESS-RUN-FUNCTION to run QUIT in a new thread. Good idea, I'll use that! > There is an internal mechanism that uses a special "application" > CAPI:INTERFACE, which provides the application menu. The default > application interface has the usual callbacks like > confirm-destroy-callback and destroy-callback. Ok, since each interface has direct access to a list of still active interfaces, a reasonable workaround is to let the destroy-callback check if the last window is being closed. -- (espen)