On 12/9/2018 7:40 AM, Hendrik Boom wrote:
On Thu, Oct 11, 2018 at 09:06:57PM -0400, George Neuner wrote:
>
> Closing the main window normally causes the program to exit ... likely the
> source of your problem.
Is this specific to Windows?
X on Linux allows one to write a program that starts up windows after it's
running, and that it can create and destroy windows at will.
That is, the program is in charge of its windows rather than the window
manaager being in charge os the program.
Technically, Windows terminates an application when the main (1st
created) thread terminates - any other threads created by the
application also are terminated (and not necessarily gracefully). The
typical structure of a GUI program has the main thread registering a
frame window for the system to communicate with. It is up to the
application how to respond to WM_EXIT, etc. messages, but if the
application doesn't behave as expected it confuses users.
As a technical matter a program that wants to receive system messages
(exit, shutdown, sleep, etc.) only needs to register a message queue,
but you get a message queue automatically when you register a window.
It will not receive GDI (graphics display) messages without creating an
actual window.
Which way does Racket on Linux work?
Unfortunately I don't know that. I'm somewhat familiar with X
programming, but I have not investigated what Racket does.
George
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
