New Value List: Comments

Hi David,

Great addition! Please would you consider the following features for the Value List component:

1) Add the ability to display the List Name, similar to panel, if it changes from the default.

2) Provide a dropdown list feature to chose the option as well as incremental steps. (just noticed the context menu)

3) In the editor provide some list management tools. Move up or down, sort (both on word and integer as an option)

4) Create a "gallery" of lists similar to Gradient

Replies to This Discussion

Permalink Reply by David Rutten on March 3, 2011 at 9:52am

1 and 3, of course. I'll get around to this eventually.

4... hmm. What sort of lists would you often use. And what's stopping you from creating a UserObject with a predefined list. Reason I don't like this is that almost none of the objects have Presets. If this is indeed needed, it should be added everywhere where it makes sense under a single unified UI. Sliders, TextPanels, ColourSwatches, GraphMappers etc. etc. they could all have presets.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Danny Boyes on March 3, 2011 at 11:17am

So far I've only used this with a Resolution Quality setting where Very Low, Low, High, and Very High output 4, 3, 2, 1 to a division component as the denominator. But I was thinking of using this in conjunction with the Stream Filter to bring through some predefined image resolutions 1024x768 etc. Or for a collection of different dash and gap lengths for the Dash Component with titles like Dash, Centreline, dots, Dash-Dots etc.

BTW there is a bug with the Dash component when you select the curve directly from the component it always previews as solid, only when you extract and hide the parameter does it display correctly.

In an ideal world I would rather make the collection of components into a user (group of) components rather than have 5 value lists saved, and different panels saved with different gap lengths etc.

Permalink Reply by Luis Fraguada on March 3, 2011 at 10:16am

5) Allow the value to be a string (do other types make sense here?). Currently if it is a string, it returns <null>...

Permalink Reply by David Rutten on March 3, 2011 at 2:17pm

It does support strings. The part to the right of the equals symbol is an expression, so it could be a boolean, an integer, a floating point number, a complex number, a string, a point or a plane (as all of these types are supported by the Expression language in GH.

Just encase the value in double quotes and you're fine.

David Rutten

david@mcneel.com

Poprad, Slovakia

RSS