I need to do 2D drawings for a Rhino project. I can put a Object Name in each properties, but the leader command does not seem to allow the use of the user assigned Object Name field. Under the fx menu it can only use the hex object name. It also cannot use the block name.
I cannot understand why these was not allowed.
Dev’s could you please allow the leader to work with the Object name?
A part number field would have been handy as well. I guess, for now, I will have to put them both in the name field, such as: 00000 - Bolt
What I want to do is, just click on a object and drag out a arrow leader that displays my name for the object or the block name.
Does anyone have some tips on doing object names and part numbers in a callout type assembly drawing?
To use the script, extract and save the .rvb file from the attached zip archive, then drag and drop the saved rvb over an open Rhino v5 window. This will load the script, set it up to load on startup in the future and register the alias
NameCallout
that will run the script much like a regular command. An alias can be typed or added to a toolbar button or keyboard shortcut (F-key). Note the script names unnamed block instances to the block definition name.
I’ve been trying to get this to work with Rhino5 without success, the leader doesn’t appear where it should, perhaps the command syntax has changed. And perhaps this function is now built in and I just haven’t found it yet?
In any case, having struggled a bit I modified it to use AddLeader instead of Leader, and it seems to do the job for me now. NameCallout.zip (733 Bytes)
David, not sure what i’m doing wrong with this. I loaded your version and ran from Monkey and got this “type mismatch in parameter. String required” error.
Any suggestions appreciated.
-Robert
Robert, did you try Pascal’s original script? Perhaps give that a go first, the change I made was only to use AddLeader rather than Leader, passing the point array across directly rather than converting to a string. Nothing was changed in the top part of the script (line 7 where your error report comes from).
I don’t know about Monkey, I searched for it and it seems to be something for Rhino 4?
I just dragged the .rvb file into one of the Rhino 5 windows to install it (and repeated to overwrite each time I modified it, which was nice, no need to uninstall), once done entering NameCallout from the command line ran it.
David
Complete n00b to scripting. How could I edit this script to not place a leader but just place a text object via the Text command? I have a bunch of parts that I just need to place a label inside the perimeter without the leader extension line.
Hi People, drafting and tagging objects create a huge work load on me .
So is there any improvement on this script. How can we make this work in “Layout” ?
I know the “leader” command work in “layout” . So also by using “fx” button you can directly give the objects name to the leader. If we could just make your “namecallout” work in “layouts” window.
Maybe also if you can add an “autimatically name giver” optipn. So left button gives the names, right button gives the leaders object name written on it.
I fixed a problem with the script - stupid on my part - I’ll attach the fixed version here and then update my post above. NameCallout.zip (722 Bytes)
Also, this fails in V6, I’ll take a look at that.
To make this ‘work’ in layouts:
Activate the detail, run the script inside the detail.
When done, select the leaders and run this command: testChangeSpace
For the automatic naming, I am not sure what you mean but you may want to use this macro on the left button:
