It used to be that when you ran a program like this ;; isl+ (require 2htdp/image) (require 2htdp/universe)
(big-bang 10 (to-draw (lambda (x) (circle (+ (* 10 x) 20) 'solid 'red))) (on-tick sub1) (stop-when zero?)) The window would shut down. But people wanted it to stay open so that they could see the final score of their games etc. I guess I could add a close-on-stop clauses for programmers such as your son but it sounds almost like he's ready to move on to racket proper, as in use the Windowing API directly. He may also be interested in Jay's variant of 'universe', which is faster (and comes with sound) or Neil's (experimental) 3D version. I conjecture that they are both more open to extensions than my teaching versions -- Matthias On Jun 21, 2015, at 12:33 PM, John Carmack wrote: > My son's game has a level editor as well as a game loop, and we switch > between them. However, each new big-bang call creates a new window, leaving > the previous ones inert on the screen. How can we close the windows? > > > -- > 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. -- 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.