My wish list

Like others have done here, I figured it was time for me to post my grasshopper wishlist. Many of the first things I post here will have been posted in various places or in messages to David, but this way everything is consolidated and people can share their thoughts.

1. Cluster rollover tips
Id like to be able to create rollover help text for each cluster input. This could be a right click thing once the cluster is created or something specified before creating the cluster (a string input for the cluster input arrows?)

2. Disconnect all outgoing
I'd like to be able to right click on an output of any component and disconnect all wires coming out of it.

3. Disconnect all selected
It would be cool if you could disconnect all incoming or outgoing wires from all currently selected components (instead of just one at a time).

4. List item dynamic slider
There has been a lot of discussion about dynamic range sliders and the issues that they would cause. Id like one specifically for list item selection. This would be an integer slider that would have a range of 0 to the list length-1. If the range remaps and the previous value is no longer available, I think it's best to have the current value stay as close to the previous value as possible.

5. Cluster slider/toggle inputs
I think it could be valuable to cluster a series of variable inputs (like sliders or toggles) to make a sort of options cluster. In this case you could just have a list of sliders and toggles each connected directly to a cluster output arrow, select all and create your cluster. This would be great with the value list component as well.

6. Have a component that could output the x and y location of actual components on the canvas relative to the top left corner... Not sure exactly what you could do with this but I think someone could do something interesting with it.

7. 3d MD slider. I see the option is greyed out and don't see a way to activate it... Still under development? Seems like it could be just like the color picker. Would be cool.

That's all I can think of right now. I'm sure there will be more to come in the future.
Feel free to comment.

-Brian

Replies to This Discussion

Permalink Reply by Rémy Maurcot on December 25, 2011 at 1:11pm

Hi david, for the slider compoment it's possible connect number for min and Max values ?
Thanks for your response

Permalink Reply by Martin Dembski on December 18, 2011 at 6:20am

Hi,

I also have a suggestion,

10. adding a tolerance value input for solid difference, solid intersection and solid union to be able to change the used tolerances for each solid boolean solution differently and parametricaly, because sometimes it is quiet annoying to change the tolerence everytime manualy in the document properties when you changed something in your definition.

David, would this be possible?

Best,

Martin.

Permalink Reply by Khizer Ishtiaq on December 18, 2011 at 1:12pm

Yeah, that would be a handy option, if it's possible

Permalink Reply by Manuel on December 21, 2011 at 12:45pm

11. Touch screen mode: if you switch to this mode, the inputs and outputs from components has bigger area-radio to "click". This will be handy for tablets screens and a friendly finger use :D

Permalink Reply by Khizer Ishtiaq on December 24, 2011 at 5:46am

12 - Animate slider have a transparent background option, if possible

13 - Multiple slider animations -

Although one can link all the other variables to one single slider but Multiple Slider Animations would be handy for Permutation Animations where multiple variables can be sequenced for better visualizations

Say we have 3 variables, A = 1- 100 : B = 50 - 600 : C = 100-200

Animation start with A=1, B=50 and C goes from 100-200 : then A=1, B=51 and C = 100-200 and once B gets to 600, A turns to 2... and so forth

And doing this manually takes a lot of time...

Permalink Reply by Martin Dembski on December 24, 2011 at 6:22am

Yes would be nice.

To achieve 13 you can have a look at the Centipede plug-in for Grasshopper.

With this plug-in you can keyframe an animation using sliders.

Permalink Reply by Khizer Ishtiaq on December 24, 2011 at 10:59am

I have experimented with some definitions using Centipede, but the issue remains the same with Centipede as the key here is the steps, B can only move to next value if C has completed it cycle, same goes for A ... Whereas keyframing just allows one to time the variables to jump in at defined keyframe ranges and not cycle (if i am not mistaken)...

Permalink Reply by Martin Dembski on December 24, 2011 at 4:41pm

Ah, ok, you want to create a cycle.

Sorry, I think I misunderstood your first comment.

But I still think it is possible using Centipede you just need to calculate all steps, in your case starting from C = 100-200 = 100 steps multiplied with B = 50-600 = 550 steps multiplied with A = 1-100 = 99 steps equals a total amount of 5500000 steps (max. of timeline if you want to have all steps).

To get the single values for B and A which are applied to the values in C you need to round and divide the numbers again like you multiplied it before.

Means when you are for example at frame 450: C = 150; B = 56; A = 1 etc.

But I agree it would be nice to create this much simpler without needing all of this expressions (and without using C#, VB or Python).

Permalink Reply by Khizer Ishtiaq on December 25, 2011 at 8:24am

Thanks Martin for detailed breakdown of the procress... That's why i wished for the Multiple Slider Animations, since manually the process takes a lot of time and one has to redo all the calculations and change the range of keyframing sliders every time the variable range changes....

Permalink Reply by Brian Harms on January 29, 2012 at 8:39pm

I thought of something else that might be nice to add - custom tooltips for custom script components. Putting the script component in a cluster to get custom tooltips via cluster input arrows doesn't work very well.

Maybe something that could show up when you right click on an input or output?

Also custom tooltips for cluster outputs would be nice.

Anyone opposed?

Permalink Reply by David Rutten on January 30, 2012 at 2:33am