Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Hi Robby Thanks for this! Dan On Sun, May 29, 2016 at 9:57 AM, Robby Findler wrote: > I've pushed another attempt. This one special cases 2htdp/image images > so they should be now equally efficient in both write and display. It > also makes things so that write and print both work the same no

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

I've pushed another attempt. This one special cases 2htdp/image images so they should be now equally efficient in both write and display. It also makes things so that write and print both work the same now (print is being called implicitly when you just return a value at the top level). Robby On

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Ah, thanks for the clarification. I don't see how I can reasonably support this for picts (because the `dc` procedure is used a lot), but maybe DrRacket can collude with the 2htdp/image library to get display's speed and print's safety. I'll think more about it. Robby On Tue, May 17, 2016 at 7:5

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Hi Robby I only used the same bitmap for convenience of example. I have cases where every bitmap is different! I hope that the eventual outcome is fast *and* secure! At the moment my workaround is to (display ...). Dan On May 18, 2016 8:52 AM, "Robby Findler" wrote: > Sorry it is taking me s

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Sorry it is taking me so long to look into this. One piece of (not so useful to you who want an actual solution!) information is that you've pointed out a security hole in DrRacket that I thought I'd closed, but apparently have only partly closed. If you run the program below, then DrRacket itself

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Hi Robby While that works for my minimal test with a single bitmap, the behavior still occurs for composite constructions. New sample code below: DrRacket, version 6.5.0.4--2016-05-16(2109b26/a) displayln: 0 milliseconds result: 1838 milliseconds Cheers Dan #lang racket (require 2htdp/image

Re: [racket-users] DrRacket: Laggy when rendering images as results vs display-ing

I've pushed a fix that reorders the cases in the code that handles printing so that you should see similar performance for these two now. I'm not completely confident in the change but let me know how it works for you. Robby On Sat, May 14, 2016 at 4:41 PM, Daniel Prager wrote: > Displaying bitm

[racket-users] DrRacket: Laggy when rendering images as results vs display-ing

Displaying bitmaps in DrRacket using 2htdp/image is near instantaneous when (display)-ed, but takes quite a while when shown as a result. The effect gets very bad when lots of images are combined with (beside) and (above), while (display)-ing remains fast. Racket version is 6.5. Dan Sample co