Can you tell me all the settings of your _OneView command? With the default, I don’t seem to be able to get what you state. I think I am able to reproduce once I set “ReturnCPlaneToTop=No”. Is it the same that you are seeing?
Oh yes, by switching I think I can see this as well. At this point I haven’t tested anything in the debugger, but it seems that the CPlane “does not stick” once one tries to pan or rotate the view. Is that right?
You see, perspective and orthogonal views behave slightly differently, enough that probably the same code will not get to the same results. Generally, I think it’s a mistake that _OneView is applied indiscriminately to all views. It only makes sense in perspective views IMO.
Well it wouldn’t be a good plan, one that bases itself on releasing a product with features that are undocumented, or wrongly documented. If it did go into a released branch, it would have required immediate attention or the cost of delaying shipping.
Yes, but previously, one couldn’t add virtually any feature during the lifetime of an entire version of Rhino for the reason that it would put the Help files out of date - at least that was the argument that was often given.
What I’m trying to say here is that should no longer be an argument, and fixing/publishing a Help page (depending on the change) may not require a whole lot of time.
And you know as well as I that there are still quite a number of “undocumented” features in Rhino…