On Jun 22, 2015, at 11:31 AM, Jens Axel Søgaard <jensa...@soegaard.net> wrote:
> John Carmack: > 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? > > > Matthias Felleisen: > 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. > > If I understand correctly, a manual > > (close-all-big-bang-windows) > > callable from the REPL would be enough in this case? This is where teaching comes in, How do you justify a function of NO arguments with the rules of algebra? So far this design guideline has produced the smoothest possible path from pre-algebra courses through Bootstrap, Program By Design, Picturing Programs, HtDP, all the way to 'Hell' (that's my software dev course for juniors). [Even if the programmers/students don't get it, straying from this design principle has always gotten me into trouble eventually.) -- Matthias -- 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.
