Hi Dar,
Thanks for the reply. How might the message queue affect an
attempt to quit a standalone? It is a little strange that this
doesn't cause any problems if I make a simple button containing
no more than a mouseUp handler and a quit command, while there
is a problem if I click the close-box to quit the standalone.
FYI, trapping the closeStackRequest message and closing all
other stacks while subsequently issueing a quit command from
there doesn't help, because the closeStackRequest message
doesn't seemt to be triggered by a click in the closebox.
If anyone has an explanation for this, I'd like to know about
it. If I don't solve this problem, I'll simply have to disable
the close button on windows, which is a very unelegant way to
solve it.
If you'd like to try for yourself, the standalones are available
here:
<http://salery.economy-x-talk.com/main.html>
Best,
Mark
Dar Scott wrote:
On Jun 7, 2005, at 7:08 AM, Mark Schonewille wrote:
When I close a Rev 2.5.1 standalone in Windows using the close box in
the top-right of the window, the process appears to keep running, even
if the closeStackRequest contains a quit command.
That can be caused by a nonempty message queue. The popular clock
script going around might do that. It doesn't have a graceful way to
stop, the last I saw.
Dar
--
eHUG coordinator
mailto:[EMAIL PROTECTED]
http://home.wanadoo.nl/mark.sch
http://www.ehug.info
Please inform me about vacancies in the field of
general economics at your institute. I am also looking
for new freelance programming projects.
_______________________________________________
use-revolution mailing list
[email protected]
http://lists.runrev.com/mailman/listinfo/use-revolution
