Just had a thought while reading yet another forum post describing how to create multiple objects and change visibility in scenes and all that.. It's obviously a brute force approach.

Then I had a thought.. I recently grabbed the FlightPath script. Even though I haven't used it yet, I get the idea.. i.e. make a sequence of lines/curves that the camera will follow...

Is there an 'OnSceneChange' notification in the API? I'm thinking (frankly without thinking through it very much) that a similar thing could be done with an object.. no? specify a path, an object and do a move command along the path on scene change..

Is this way off, or is there something to it? As I said, this was just a flash thought as I was perusing..

I second that emotion... Currently trying to print out for a presentation with a very complex Sketchup file. Every move I make is followed by 30 seconds of excruciating nothing.

And... Unless I'm missing them:

• a measuring tape..? I can count grid lines, but...
• and some way of telling whether the Document Settings page specification and the printer setup actually have met each other.

I just posted about this under another topic. I second that emotion, and add that I, too, am a guide line user. Ironically, it can be frustrating fighting the inference engine to place the guidelines. But I do believe strongly in the use of guidelines.. In my other post I suggested the possibility of scoping the inferencing. Only the current layer or context.

Great idea. I will steal it and make use of it immediately.

Just an added clarification, probably known already, but switching off scene transitions prevents the flyaround action and jumps quickly.

One thing I would like to see is the ability to align the protractor and/or section planes without having to find an orthogonal face somewhere. The 'keep a cube around' idea is a workaround, but I find myself reaching for the arrow keys as in inference locking on an axis direction. This would be very helpful, especially for the protractor/rotator tools.

I've seen other requests for this scattered around. This must occur to everyone at some time or other. I'd like to be able to disable the inference engine so I can control the mouse input. Similar to ACAD, etc, where there are a set of snaps that can be enabled and disabled. Alternatively or additionally, it would be helpful to be able limit the inferencing to the current layer, current scope/context, etc.