Continued developer absence

Apologies for my long periods of absence and poor attendance over the past few months, I've been reasonably busy with travelling, workshops and client visits.

I'll be at Siggraph in early August (New Orleans) and I'm throwing every available inch of development at this deadline. It's clear now that I won't be able to solve all reported bugs before then, but I would nevertheless like to release a new version in the upcoming week.

So I'd like to ask for a list of the most pertinent bugs/lacking features which need to be solved asap.

Goodwill,
David

--
David Rutten
david@mcneel.com
Robert McNeel & Associates

Replies to This Discussion

Permalink Reply by David Rutten on July 25, 2009 at 5:16am

I'll add a Ref-Geometry -> Guid component. It's easy enough.

Permalink Reply by David Rutten on July 25, 2009 at 5:21am

Hi Luis,

>if I update the definition somehow, the param viewer output goes orange.

I've rewritten most of this code, so the problem may have gone away already.

>Also, could we get a scroll in the param viewer.
Already added this. I also added a visual mode to the ParamViewer which draws the data tree instead of just listing the paths.

>Oh, and as if there were not enough requests...any way to change the component view type
>(icon or text) by component? For the most part, I am fine with icons, but I would like to name
>a few here and there and see it on the component instead of making a note.
I also want to put extra options into all parameters that allows you to change the wire-drawing modes (just like the Receiver param). I'll see if I can figure out a way to add this option without bloating the menus even further.

Permalink Reply by David Rutten on July 25, 2009 at 6:51am

Luis,

>Oh, and as if there were not enough requests...any way to change the component view
>type (icon or text) by component?

How about if you start the name with a "!" it forces text display on parameters and components? Or is this solution way to old-fashioned?

Permalink Reply by Luis Fraguada on July 25, 2009 at 7:37am

Hmm, I'd be fine with this, seeing as it would not add anything to the menu of the component...

I am not sure how it would work for everyone else though...its sort of 'another' way of doing something in GH. So in order to keep it in line with how people already work the menu might make more sense...

How about doing something like the Ctrl+Q / Ctrl+Shift+Q for previewing selected components? You put it in the View Menu by the Draw Fancy Wires and Icon View and use a Ctrl/Ctrl+Shift + Keyboard key to shortcut it. This way it does not add anything to the individual component menu?

Permalink Reply by David Rutten on July 25, 2009 at 8:16am

Yeah you're right. It's too undiscoverable.

Even though I can add a menu+shortcut override for selected objects, the option still needs to be in the menu somewhere.

Permalink Reply by Andres Gonzalez on July 25, 2009 at 9:02am

Hi David

The UNDO, please, see what you can do about it. Our students always expect that to work.

See you in New Orleans!

Andres Gonazalez
www.rhino3d.com
www.rhino3d.tv

Permalink Reply by David Rutten on July 25, 2009 at 10:05am

Andres,

I know, but I won't have time for this I think.
I'll try, but don't hold your breath.

Permalink Reply by Tuan N. Tran on July 25, 2009 at 11:19am

David,

For the intersect components, can we have true/false return for the event?

Permalink Reply by David Rutten on July 25, 2009 at 1:00pm

Hi Tuan,

instead of adding outputs to all intersection components, wouldn't it make far more sense to simply test the results for null or zero-length lists?

Permalink Reply by David Rutten on July 25, 2009 at 1:23pm

Tuan,

see this screenshot for how the IsNull component works: