Hi PJ, I'm trying to avoid single-click events inside Grasshopper. At the moment, the worst that can happen when you click somewhere is that your selection set is changed. I'd rather not make the Grasshopper UI that 'touchy'
Having a master switch component which controls the enabled/disabled state of any number of child components is something that sounds reasonably intuitive, accessible and efficient (in terms of screen clutter/real estate) to me. I think I'll try and develop this idea further. -- David Rutten [email protected] Robert McNeel & Associates On Mar 5, 1:09 pm, PJ <[email protected]> wrote: > Yeah, I guess my method is perhaps a little overcomplicated; I > actually tend to use it (or rather, an expanded version of it) for > when I want to switch between several different streams or in the body > of larger VB components that I only want to use occasionally (for > example, a 'custom bake' script to add geometry to the document with > layernames, user text etc or something to produce an output file of > some kind); which brings me onto this: > > What would be nice in the next version would be a 'button' component > that when you click it will run an update of all attached components > only once each time you click it (i.e. is true for one update cycle > and then automatically switches back to false for the next one). > Granted, probably not useful at all for most people, but my personal > panty-drop factor would be through the roof. Or perhaps the floor. > > Paul > > On Mar 5, 9:04 am, urbansurgery <[email protected]> wrote: > > > not to sound too grumpy about it ;) but a cull is the same as a > > dispatch without the redundant B stream > > > same input fewer outputs - saving memory no?
