I use excel to create sets of rhino commands to carry out all sorts of repetitive and mundane tasks. I’m currently testing some of my most commonly used scripts in WIP and I noticed that the circle and sphere commands work differently.
In R5 drawing a circle or sphere with a radius would look like:
In R6 this doesn’t work. It seems that if I state “radius” when this was used previously then the remainder of command falls over. I want to state radius every time to ensure that no matter what was previously used all of my commands will use the radius.
Some commands such as rotate allow syntax such as Copy=Yes or Copy=No. This syntax (i.e. radius=0.3) doesn’t work for the radius either.
I’ve also noticed that the text command now uses the new annotation styles, but I can’t see any reason why the behavior of circle and sphere would have changed.
Have I missed something? Or is this is a bug? I hope its not an intentional change.
Hi Daniel - my guess is that this is fallout from the Radius, Length and SubCrv commands being made nestable (to allow you to select existing geometry to set a command line number) I’ll test your macros and see - hold on a bit.
Hi Daniel - the problem is this, if I am seeing clearly - if Radius is not a current option - as when it’s already been set - then the full word ‘Radius’ does not refer to an option and V6 now interprets this as the nestable Radius command. Just ‘r’ is nothing (though it could be an alias, which is even messier) so Rhino ignores it if there is not a Radius or other ‘R’ option actually available. Mikko may set us straight but off hand I do not see a good way out of this as things stand now.
@Daniel_Niziolek, Mikko (developer) reminded me that you can prefix a command line option with a “/” to force it to be read as a command line option even if it is not showing -
-Circle 487.622009,639.282663,25.801 /radius 0.3
That should get you out of the woods for now at least.