Grasshopper

algorithmic modeling for Rhino

Dear GHA developers,

 

I'm about to release Grasshopper 0.8.0005 to the public. Since there are a fair amount of SDK breakages I'll post a debug version here first so everyone can test their own code before it goes out to the public. Since this is a debug version it'll be cumbersome to use and there's a lot of extra info and weird colours in the UI.

 

Download the installer.

 

For pure component and parameter code there should be little or no difference, but if you're doing anything 'special' you might run into problems. Specifically:

 

● GH_Canvas.Graphics can now only be called during a redraw procedure. The Graphics object no longer exists between paint events. There's a new function called GetGraphicsObject() which returns a non-paintable Graphics instance.

 

● GH_Capsule has been restructured and a lot of the rendering code has been moved to GH_CapsuleRenderEngine.

 

● A lot of interface classes have been changed, deleted or marked as obsolete.

 

● The User Data implementation of IGH_Goo has been removed as it wasn't operational.

 

If you have a problem running under the new SDK, please post the error message you get here and I'll try and come up with a solution.

 

I've also uploaded a new build of the SDK helpfile.

 

-------------------------------------------------

 

This is a list of changes (SDK changes not included) for this release:

 

● The deep-down-display-plumbing has been rewritten. The Grasshopper canvas is now drawn on the screen in a completely different fashion, be on the lookout for weird behaviour and novel crashes.  

● Added customizable display threshold to profiler widget.  

● Added a Reverse option on all parameters in addition to Flatten and Graft.  

● Added constant info to the PathMapper mask dialog.  

● Added 'Copy Content' and 'Copy Data Only' menu items to the text panel.  

● Improved add-on icon placement on the banner.  

● Rewrote Colour Picker control from scratch.  

● Rewrote Number Slider control from scratch.  

● Added a new Digit Scroller control to replace all standard windows numeric up/down controls.  

● Added a new Digit Scroller control as a special object. 

 ● Added a new data type for groups of geometric objects.  

● Added Create Group component (Transform tab).  

● Added Destroy Group component (Transform tab).  

● Added Merge Group component (Transform tab).  

● Added Split Group component (Transform tab).  

● Added a Transform Matrix type and parameter.  

● Added Compound Transform component (Transform tab).  

● Added Split Transform component (Transform tab).  

● Added generic Transform component (Transform tab).  

● Added Transform Matrix display object (Transform tab).  

● All Transform components now output Transformation data. 

 ● All Transform components now have optional geometry inputs.  

● Double clicking on the trackbar portion of a slider now pops up an input textbox.  

● Added a Settings browser window (File menu). Note that this is not supposed to be a true Settings interface.  

○ Fixed a problem with the popup search box not showing up sometimes.  

○ Floating parameter icons now center themselves in the space left over by the state tags.  

○ 'Export Hi-Res' menu item is now disabled if no document is loaded.  

○ Fixed a problem with tooltips on the Grasshopper banner assembly icons. 

○ Parameter flatten settings were not recorded in the undo-stack, this is fixed.  

○ Parameter graft settings were not recorded in the undo-stack, this is fixed. 

○ Fixed a bug with Curve|Line intersection and degenerate curve boundingboxes.  

○ Fixed a bug in the Shatter Curve component (thank you to])

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Views: 1396

Replies to This Discussion

it's like christmas!
release it, we'll live!  just kidding, take your time.  ;-)
Heyyyy!!! Thanks!!! I'll try it!

First, I just wanted to say thanks for all of your hard work and for giving us the opportunity to make revisions to our third party builds before the next official release.  I had a chance to run a few diagnostic tests earlier this afternoon on the latest build... and found only one or two very minor things I had to change with the Firefly build (and this would be problems that were on features for the next release... the old build seemed to work fine).  I did run into one issue regarding the new reacTIVision component (released in the last public release of Firefly).  When I was testing it, I got an error that said the "Canvas Graphics object is only available during painting operations".  This didn't totally crash the system, but just created a breakpoint (see attached image).  You mentioned that you changed the 'deep-down display plumbing' and I'm wondering if this has to do with that.  I'm using two drawing events in this component (to draw the tick marks and another for the text tags)... is there something I need to do differently to avoid this?  Let me know if you have any ideas.

 

Oops, that's my bug. I can repeat it here and I'll fix it. It is indeed a result of the new display code (see my first bullet point in the SDK changes list).

 

Thanks for finding it.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Fixed, the bug was actually in the Markup (Sketch object) window selection code. It had nothing to do with your components.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

This is great.... David, please, do not forget to look at the Solution > Save States, and be able to delete them too later.

Oh right. I'll see what I can come up with. Thanks for reminding me.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

 

Ok, added a second menu fold-out that allows you to delete states. The whole state business probably needs a proper floating dialog at some point.

 

I also added State addition, State removal and State overwrites to the undo.

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

These sound intriguing...

 

● Added constant info to the PathMapper mask dialog.

● Added a Transform Matrix type and parameter.

 

I will let the anticipation build.

Well, don't get your hopes up too much. The 'constant info' is basically just a list of the constants you can use in the expressions (such as 'path_count' and 'item_count'). 

 

I also sincerely doubt the usefulness of customized Transforms, but I might be proven wrong about that.

 

 

--

David Rutten

david@mcneel.com

Poprad, Slovakia

Hey David,

I didn't see it in the list of new features so I thought I would send a friendly reminder as a follow up to a previous discussion regarding scientific notation.  You mentioned you hoped to include a way to set the thresholds of when scientific notation kicks in.  Including this would really help with some inaccuracies I am wrestling with caused by early scientific notation activation.

Thanks,

Stan

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service