Drafthorse is now available in grasshopper for Rhino 8! Updates include easier-to-use references to layouts and views (using the new Grasshopper.Rhino types). Drafthorse works especially well with the new “query pages” component from the Rhino ribbon, which can synchronize with the active document to keep your definition dynamically up-to-date.
Check out the revised set of examples on the food4rhino page
Nice one! Thanks.
Hello @jokamm.
I’m looking at your plugin and the question I have is, what is the Geometry parameter supposed to be under Deconstruct Detail? Hint says “Underlying geometry”.
Could you please describe it more detailed?
Great question @Screamer - I wish I could help, but I’m not sure myself. The “Underlying Geometry” is one of the properties of the Detail object in Rhinocommon, so I exposed it in the Deconstruct Detail component more out of curiosity than anything else. I was thinking/hoping it would be something like the rectangle of the detail in paperspace, but that does not seem to be the case. Not sure who the right person on the McNeel team to ask is. @Japhy do you know who would be a good person to ask about this?
@dale will have the definitive answer, which method are we talking?
https://developer.rhino3d.com/api/rhinocommon/rhino.docobjects.detailviewobject
@japhy - the .DetailGeometry property on the DetailViewObject.
Hi @jokamm
I can see a hint “Input View from Make2D Components” under DetailEdit.
Does it mean it can create Make2D to the Detail content and bring it to layout?
Or it’s about something different?
@Screamer In Rhino, the View Creation components are under the Make2D ribbon. This is a reference of where to find the View Creation components.
Drafthorse takes advantage of these existing components to avoid re-inventing view creation
I see.
Ok. Thank you for explaining.
Let me be more direct.
Am I correct, you have plans to implement ChangeSpace as well, right?
Do you think bringing the content of the Detail as something like Make2D process to the Layout space is possible in the future?
In other words, is it possible to make 3D content “flat” to the layout?
This will open the advantage to save layout to DWG format easily.
If you use the new content cache component with one layout active, then it will bake it in the active layout space".
Hi @julien2
May I bother you and ask for more details?
Can you show a working sample, please?
Go get the gh file I posted there.
It’s a test file, but you have the components to test what i’m telling you.
Hi, are there any plans to upgrade the Mac (Mx) version of drafthorse? Seems we are stuck with 0.4.1 since last November. It really looks like a supergreat Plugin and I can’t wait using it!
Thanks!
@jokamm I’m having problems installing Drafthorse. I’m using Rhino v8.9.24163.
I’ve tried installing v1.0.1 via the package manager with no success. I don’t receive any error message in Rhino so I assume it is loading properly.
I’ve also tried copying those files to the main component folder (C:\Users\PaulWintour\AppData\Roaming\Grasshopper\Libraries). I also right clicked on the *gha file to see if it needed to be unblocked but it looks fine.
Any ideas what might be causing this?
@jokamm any ideas?
Hi @jokamm ,
Thanks for your plugin ; using it in Rhino 8.
I have a few questions and remarks, as I bumped into several issues :
-First, I notice that when using your components, layouts that are referenced randomly disappear.
The page itself is still there, but it is completely empty, and it’s not a zoom thing ; there’s no more representation of the paper, and whatever objects or details that were there are gone with no possibility to undo; a kind of black hole effect. Is it a known bug ?
-I really wish there was the possibility to bake blocks or other objects to a layout.
-I don’t get why we should use boolean toggles rather than buttons in the “Run” inputs.
“Modify” or “Update” buttons on components don’t make much sense in my opinion.
I’d like to report a bug whereby the PDF that is generated through the “PDF Layout” component doesn’t follow the display style of the view :
Also, I think there should be an option to choose between a raster and a vector output.
Hi @osuire thanks for your thoughts and observations. Can you tell me more about the error that you’re having with referenced layouts? I still haven’t switched over to using Rhino 8 myself regularly, and I haven’t come across something similar in Rhino 7.
As for the buttons… well, yes, I agree that it is not in the spirit of grasshopper to have so many buttons. There are several reasons I went this way, from the curiosity of figuring out how to make them work, to the functionality/convenience of a built in switch. As for the button/toggle, I don’t know why this is the case, but there are several functions that seem to do poorly when using a button. Elefront’s Export component comes to mind. When used with a button, the effect that I’ve observed is that the canvas “locks up” - it freezes without crashing - and can only be “unlocked” by triggering the button again. I think it has to do with receiving two values in quick succession, so functionally, I have been able to use buttons to trigger these components by using a data dam to increase the time between value changes. All of the button driven components also have “run” or similar inputs, so it is possible to build them into completely automated workflows.
As far as “Modify” and “Update” buttons on components, that’s a a referencing/update issue that I haven’t figured out. The “Query” components in Rhino 8 get around this problem nicely though, and I recommend their use in my documentation and examples.
Lastly, baking to layouts, yes! I’d like to see this too! I worked on it for a bit (there’s some abandoned efforts in the codebase), but haven’t figured out how to do the minimum of baking to a layout except with the previously known method of making the layout active and using any other “bake” or block insert components. I am loathe to rewrite all the code for the nice features in other bake components (Elefront/Human/TTToolbox, etc), and I made the “make Layout active” component in lieu of this. In combination, it is possible to make a layer or series of layers active, then trigger a bake component (especially when used with a timed trigger workflow).
I would love to get some help figuring out the Bake/Insert to layouts (paperspace) feature, or, even better, figure it out and get it incorporated into one of the well-established and more commonly used component plugins.
Hi @osuire - I agree on the raster/vector output. Not quite sure how to accomplish that, it’s not obvious in the documentation from what I’ve been looking at. Do you have any development experience? Please feel free to dig into the implementation of the component. Are there any other PDF components that do what you are hoping to see? As i recall, Shapediver’s PDF writer exclusively makes bitmaps, but last I checked it preferred the ones generated in Squid.
hi, @jokamm ,
i second this. Concrete example, currently I cannot print a colored mesh.
Attached a python version that does allow option to print as Raster or Vector by author = “Dharman.Gersch”
Hope it helps you implement it.
PS: I notice some strange behavior when using toggle to save the pdf’s, it keeps on saving, until I turn toggle back to False. Maybe i’m doing something wrong, but i’ts kinda annoyong at it freezes gh.
drafthorse.gh (327.8 KB)
