OneView - Thanks

[wim (Wim Dekeyser)]

Thank you for implementing the AutoCPlane script as a new native command - OneView!!
And it works as it should

[wim (Wim Dekeyser)]

Not sure why it maximizes a viewport though. I run this in my startup commands and my template is saved as 4-view layout but this now opens with one maximized viewport.

[RIL (Rolf)]

AutoCPlane

AutoCPlane doesn’t seem to be documented as of yet. How is i supposed to function?

// Rolf

[wim (Wim Dekeyser)]

AutoCPlane never was a native command. It was a script that was originally written by Pascal and that now finally has made it as a native command as OneView (fully documented ) .

[RIL (Rolf)]

OK, now I get it. I’m slow today!

[tobias]

Hey this sounds cool!
I tried the v5 plugin but it doesn’t do anything. Is there a version that works with the current v5 SR13?

thanks, Tobias

[wim (Wim Dekeyser)]

@tobias

Is there a version that works with the current v5 SR13?

There were quite a few versions of the script floating around - did you try the one from this link?

Experiment: AutoCPlane mode as a V5 plug-in

Hi all, @theoutside , - here is a V5 plug-in AutoCPlane.rhp (18 KB) and script AutoCPlane_01_07_15.py (8.6 KB) with Giulio’s enhancements - the CPlane does not actually get changed until you release the mouse button, but the labels constantly update to tell you what the CPlane will be if you release now. -Pascal

EDIT - going through that thread a bit more, here’s a link to the version that I found useful (and that is like the current OneView command).

https://discourse.mcneel.com/uploads/default/14572/e6759000a3a9f255.py

posted here:

Experiment: AutoCPlane mode as a V5 plug-in

Update that does not flicker. (Thanks Giulio!.. Scripters, use the Draw2dRectangle function for this, not DrawPolygon…) AutoCPlane.rhp (18.5 KB) KyleMode_NoViewSnap_Label.py (9.0 KB) -Pascal

[tobias]

Yes, I tried that one but it doesn’t do anything.
I tried it on my workstation and on my laptop. Same result

[wim (Wim Dekeyser)]

Just updated that post with a link to a python script…

[tobias]

There seems to be a problam with Python.Running the script I get this error:

The object from this error is rhinoscriptsyntax. The line raising the error reads:
angle = rs.GetInteger(“Set CPlane swap angle”, defAngle, 1, 44)

What could possibly be wrong?

[wim (Wim Dekeyser)]

Yea… I remember that one. Just comment out the first two lines and that should do it.
Attached a version that works on my RH5 SR13…

AutoCPlane.py (9.0 KB)

[wim (Wim Dekeyser)]

Thank you for implementing the AutoCPlane script as a new native command - OneView!!
And it works as it should

Well…
@brian, I’m not sure why OneView is listed as a New Feature in the change log.

2015-09-25:

AutoCPlane - latest WIP

Hi Wim - I think I'd block the plug-ins for now and use the OneView command and see how that works for you -; also, TestStraightenView is another similar thing to fool with. -Pascal

… but at least now that command works as it should!

[tobias]

Still the same line gives an error: ‘module’ object has no attribute ‘GetInteger’

[wim (Wim Dekeyser)]

Tobias, did you restart Rhino after downloading that python script? Grasping at straws here until a bigger brain wakes up…

What happened to rhinoscriptsyntax sr12!?

@wim thanks for posting the dialog screenshot. The problem is with the AutoCPlane.py file. The top of the file looks like this: import rhinoscript.userinterface import rhinoscript.geometry import Rhino import scriptcontext import System import math import time import rhinoscriptsyntax as rs The last import normally loads all the modules and all functions are associated with the “rs” alias but since the userinterface and geometry modules have already been loaded in the 1st 2 lines they w…

[tobias]

Yes, I did restart Rhino…
Thanks for looking into this issue

[Willem (Willem Derks)]

Great! I saw the OneView command pass by and wondered what it did…

As a regular command name critic may I add my observations:

@pascal what is the thinking behind the name chage to OneView as opposed to AutoCplane. In my thinking the functionality of this command is operating on the Cplane: setting it based on view angle. The name OneView does not cover that. Rather it suggests a command to maximize to a single view or something. However it can be set to any arbitrary number of views right?

I get that the name is a suggestion the command is for working in one view. However that is what it enables rather than the functionality of the command.

In addition, by stacking actions in one command (auto cplane & maximizing the view) it’s easy to mistake this command for a maximize view and the user missing the autocplane.

If I as a user were to suddenly have the Cplane change all the time I’d start searching for commands with “Cplane” in it. Not view or one.

So I’d opt for a AutoCplane command and maybe macro a OneView command by stringing a maximize view to it.

-Willem

[pascal (Pascal Golay)]

Hi Willem - I was very much on the sidelines as far as the naming goes, but I think @theoutside, who was the moving force behind this, was thinking of it as a good way to work in a single maximized viewport.

-Pascal

[mikolaj (Mikolaj Jarski)]

I wish OneView labels were tuned up. Now there are different fonts and alignment within label. Perhaps the style could match the one of viewport name?