Let me add my two cents. I've only been using the API for a couple of days now, and I can see that dimensions aren't accessible from it. This would be very important to me. I can see it's been requested a couple of times already...

Thanks for such a great tool.

Just thought of another one. Last night I tried to create a script to let me control the camera like you would in a video game: WASD and mouselook. Turns out that key press events are consumed by shortcuts before they can get to a script. Also, you can't copy the shortcut keys, change them temporarily while your tool is running, and then restore them when it's deactivated. A way around this would be nice. I know the walk tool lets you use the arrow keys, but it would be nice to a) be able to change those keys and b) use mouse look at the same time

Thanks, Whaat. That did the trick. So the reason behind this is that SU was only invalidating a default area of the screen around the first point because I didn't implement getExtents?

I'm pretty new at this, sorry. I've been looking at the linetool.rb script that comes with SU, and I'm having trouble with it. When the tool is in the "picking second point" state, and its draw method is being called, the line that's drawn between the first point and the current mouse location is not always "complete". That is, the line extends from the first point to a point in between the first point and my mouse and stops. When I click to select the second point, the construction line that the tool is supposed to draw works fine. It's only the temporary graphics in between selecting the first and second point. I modified the draw method to use view.draw_points to draw the first point and the point where the mouse is currently, and the points show up in the right place. Am I missing something? What is wrong with this example?

The point just floating out there is where my mouse pointer was when I took the screenshot.