Re: [racket-users] Preventing browser frame from terminating evaluation thread?

I don't have an explanation (I just guessed exit was being called somewhere), but the exit handler did have an effect. The example program quit with "Interactions disabled" in DrRacket, whereas this program does not (and does display "Called exit"): #lang racket (require browser) (define

Re: [racket-users] Preventing browser frame from terminating evaluation thread?

I don't think setting the exit handler will have an effect. The example application quits because an implicit `yield` finishes when the window is closed, and then the GUI handler thread has nothing else to do, so it exits. You could add an explicit `yield`, to allow events to be handled, and then

Re: [racket-users] Preventing browser frame from terminating evaluation thread?

It's a little ugly, but you can change the exit handler: (exit-handler (λ (x) (displayln "Called exit"))) -Philip On Mon, Apr 17, 2017 at 8:57 PM, Matt Jadud wrote: > Hi all, > > I would like to spawn a browser frame, but I'd like it if the frame did > not terminate the

[racket-users] Preventing browser frame from terminating evaluation thread?

Hi all, I would like to spawn a browser frame, but I'd like it if the frame did not terminate the thread when I close it. I'm having a hard time figuring out what I should override/augment or catch so that I can spawn the frame from within a GUI application, let the user close the frame, and