As you (hopefully) noticed, I've spent a bunch of time this release cycle trying to improve drracket's interactivity and I'm at the point now where I could use a little help testing. So, if you have any time to play with the latest from git (or a nightly build after tonight) and notice that certain things you do make drracket more sluggish, can you please let me know?
There is a specific thing you can do to give me good information about what's going on when drracket feels sluggish. Specifically, alt-click (or maybe control-click, depending on the platform) on the number of megabytes (the "MB" in the bottom right corner of the drracket window) and you should get a window with three buttons. Click "start following log" and then do whatever it is that feels sluggish a bunch (maybe for 5 or 10 seconds) and then click "stop & dump". Send me the content of the window and a little explanation of what you were doing to give me some context and I'll see if I can find something to fix. Thanks! Robby
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
