[racket-users] Re: Trying to understand racket/gui and racket/draw

2016-09-18 Thread George Neuner
On Fri, 16 Sep 2016 06:04:09 -0500, Robby Findler wrote: >You could draw into a bitmap and then have on-paint draw that bitmap, too. > >Robby Yes. "Double buffering" with an off-screen bitmap is the best way to minimize redrawing. However, it also should be pointed out that the DC has a clippin

Re: [racket-users] Re: Trying to understand racket/gui and racket/draw

2016-09-16 Thread Robby Findler
You could draw into a bitmap and then have on-paint draw that bitmap, too. Robby On Fri, Sep 16, 2016 at 2:53 AM, Jens Axel Søgaard wrote: > As Alex writes the operating system (the system GUI) might erase parts of a > window at > any time. Therefore you need to do all your drawing from within o

Re: [racket-users] Re: Trying to understand racket/gui and racket/draw

2016-09-16 Thread Jens Axel Søgaard
As Alex writes the operating system (the system GUI) might erase parts of a window at any time. Therefore you need to do all your drawing from within on-paint. http://stackoverflow.com/q/16084690/23567 /Jens Axel 2016-09-16 7:09 GMT+02:00 Alex Harsanyi : > According to the documentation for th

[racket-users] Re: Trying to understand racket/gui and racket/draw

2016-09-15 Thread Alex Harsanyi
According to the documentation for the canvas<%> interface you cannot rely on the canvas not being cleared (http://docs.racket-lang.org/gui/canvas___.html?q=canvas%3C%25%3E): Even when the canvas’s style suppresses explicit clearing of the canvas, a canvas may be erased by the windowing system