-
For the text dot, what does the secondary text do?
-
And could the text dot support a colour input too?
-
As for layer querying, I would really like to have a dedicated item selector for this. To illustrate, I used Human’s item selector:
What I would like to have is an input box where you could type in a layer name and have autocomplete (like in VSCode) to suggest possible values for layers names. It could have buttons to restrict search only to parent layers or to filter for child or grandchild layers.
E: Recording cut off the part where I point that the circle is in the “circle” layer and the rectangle in the “I want this layer” layer.
E2: Basically this, but all in a single item selector by enabling the parent layer button in the item seletor:
Note the big difference in the component size that is enabled by stripping all the nested child layers out of the layername.
Just to add on the text dot:
I would appreciate if we could choose to give depth to the draw order of the text dot position.
1 Like
Thanks for your suggestions. The secondary text doesn’t really show up unless you bake the Text Dot. The same is true when you create a new Text Dot in the Rhino UI. You can set the Primary Text which is the text that gets displayed, but there is a Secondary Text section which you can add whatever additional text that you want. You can see these in the Object Attributes panel when you select the Text Dot in the viewport.
Also, we decided not to add a Color input directly on any of the annotation components. We felt that it would make these components even larger than they already are and that you could use a Display Component, or the Model Object Attributes component to set the color that way.
Lastly, your suggestion for querying layers is a good one. It’s one we’ve discussed internally too. In fact, this is on our roadmap and should apply to any parameter which incorporates one of those list boxes. The thinking is that there would be a text box located above the list box where you could begin typing in a filter name and it would filter the items shown in the list box based on your filter. So, this is planned, but I don’t have an update as to when that might occur.
1 Like
You should be able to set the Draw Order in the Drafting Attributes component. Essentially you would connect your Text Dots to the Geometry input of the Model Object Attributes component. Then create a Drafting Attributes component and set the corresponding list of Draw Order input values. Finally connect the Drafting Attributes output to the Drafting input of the Model Object. This should fix this issue (at least when the text dots are baked).
1 Like
Setting the draw order isn’t really going to solve the issue for perspective views as it is just going to slam a text dot to the front or back no matter what camera angle is being used. This feature is something that needs to be adjusted in Rhino’s core display code and is not something that a component can fix at the moment.
2 Likes
Thanks for the explanation!
Yes exactly, it should be useable in all sorts of circumstances, it would be useful for Rhino.Inside.Revit too! I don’t know what the possibilities are to add specific filtering options and buttons on the component based on the inputs (e.g. for layers that might include filtering parents only as I mentioned, but circumstances may differ).
As for not adding colour to annotation components, I can see the reasoning, but I think it’s not ideal either that you need to place another large component (even though you can hide the unused inputs).
Now that I mention it, I would like to toggle show/ hide the unused inputs with a hotkey. I don’t see this in the shortcuts list 
This has been fixed and should be available in the next WIP release. Thanks for reporting this.
1 Like
Thanks for fixing!
I would use GH point clouds every day. Yeah, I know I’m the only one.
Rhino 8 WIP can now reference Point Clouds using the Point Cloud parameter (Params->Geometry->Point Cloud). We haven’t really exposed any components which lets you deconstruct a point cloud, etc… but you can at least access them now in GH as a native type. You can even convert a mesh into a point cloud (using the vertices as a PC). So, it’s not a complete solution yet… but it’s a start 
5 Likes
Great plans! Thanks for the blocks and the already explained changes!
Is there a plan to include native camera attributes, view assignation, display modes, and increase Make2Ds options? Also camera movements and clipping planes. Also, a layout sheet tab toolbox where details can be created, annotated and exported as batch pdf.
I hope everyone sees what I mean,
2 Likes
The latest WIP release does contain a few components for creating views, etc. Under the Rhino tab, you should see a category called Viewports with 4 components. The Query Model Views component will return a list of all available viewports (in the model, or page layouts). The Model View component lets you define or modify views. If you right-click on this component you can access some additional parameters that can be set and if you bake it, it will create a new Viewport in your model/page. The Viewport Frame component lets you set all of the parameters which define an actual view (ie. camera in your question) such as the camera location, the target distance, etc. If you bake this component, it will create a new Named View with that specific view frustrum. Lastly there is a Zoom Extents component which, well, zooms the viewing frustrum so that all geometry fits inside the view.
Unfortunately, we haven’t exposed any way to create detail views as that’s a bit tricky. It is on our road map, but it isn’t implemented yet. Also, section/clipping planes are also on the list, but we aren’t sure when those will be added.
6 Likes
I guess detail management will need to be fixed in rhino before it makes sense to implement it in GH 
2 Likes
This is interesting especially when many named views can be created at once. I’ve been doing that with a script until now… Below is a definition that should bake two named views but only one is baked and I couldn’t delete it anymore.
I’m struggling to bake two named views at once. Also when I plugged the paths directly to the view name input, it raises an error…
bake_zoom_extents.gh (20.0 KB)
I do like this new components. Quite useful but still missing one big feature: a BAKE entry for each component that can be triggered from a button.
In my projects I do trigger multiple bake actions for different components using the Elefront BakeAll feature.
5 Likes
For simple script inspections or nicer previews, I often still default back to Human’s Custom Preview Lineweights. Would it be possible to create a similar component that does: line weight, colour, draw order (display in front basically, but with an index so you can determine the draw order for several portions of the script independently)?
AFAIK to get this to work with the new components is quite involved as it requires lots of components, data, layers, etc.
2 Likes
@AndyPayne there appears to be a bug in the Text Dot component, if I bake the text dot from the top position, it does not adhere to the layer I chose in the bake dialog.
Instead, the baked text dot consistently appears on the current layer or another layer, but not the layer I chose.
This is in Rhino 8.0.23080.12305, 2023-03-21 on Windows 10.
Is there some kind of a BakeUpdate (select a previously Baked object and replace it with a new one out of the oven) on the TODO list? Then we could tie GH and Rhino history together and do some really crazy stuff.
Yes. It is on our todo list
5 Likes