Ahh the panty drop factor...I completely missed that one :) Btw, what bar are you going to where you're programming conquests are pickup lines? Since we're on the subject how are the women there in Slovakia?
-Damien On Mar 4, 3:27 pm, David Rutten <[email protected]> wrote: > Hi Damien, > > that would be the most obvious (old school) implementation. Here are > two others which might be interesting: > > 1) Create a Disable/Enable switch somewhere. You can drag tentacles > from this switch onto components and then disable/enable them all by > double clicking the master switch. Two problems with this approach; > it's not clear what should happen if one component is controlled by > more than 1 master switch, and it adds yet more clutter onto the > screen. > > 2) Create a Disable/Enable Region object. You can sketch a (freeform?) > region onto the canvas and drag components into and out of this area. > Whenever they are inside they are subject to the region state (which > can either be disabled or enabled). > > Both would take significantly more work than your suggestion of course > (which I could probably implement in 15 minutes), but they have a much > higher panty-drop factor. > > -- > David Rutten > [email protected] > Robert McNeel & Associates > > On Mar 4, 9:00 pm, damien_alomar <[email protected]> wrote: > > > The most elegant solution IMHO would be to have a "Calculate" feature > > for each component. We could turn off the calculations on a per > > component basis just as we do the preview. The preview could be a red > > line around the center name part of the component when calculate is > > off, yet the solution is still valid. When the solution has expired > > the center name part of the component could have a thick diagonal red > > line pattern, possibly going from top left to bottom right. That > > would create a "rotated checkerboard" pattern when a component is not > > previewed, not being calculated, and has an expired solution. Of > > course you'd also need a hot key for toggling the calculation state of > > the current selection :) > > > -Damien > > > On Mar 4, 11:54 am, David Rutten <[email protected]> wrote: > > > > Damiens solution is probably the most elegant within the current > > > framework. But it's still a round-peg-square-hole type of deal. I'll > > > let this fester in my mid-brain for a while, perhaps I can come up > > > with a neat solution. > > > > -- > > > David Rutten > > > [email protected] > > > Robert McNeel & Associates > > > > On Mar 4, 5:34 pm, damien_alomar <[email protected]> wrote: > > > > > I think you guys are both complicating this too much. Just set up a > > > > Boolean Gate/Dispatch component with the list in and a boolean toggle > > > > switch. Hook the rest of the stream up to A and when you change the > > > > toggle to False it will stop the stream. > > > > > Best, > > > > Damien > > > > > On Mar 4, 6:28 am, urbansurgery <[email protected]> wrote: > > > > > > I also do this a lot, but rather than script it its oftentimes easier > > > > > still to use a Cull Pattern component with a Boolean Parameter (red > > > > > circle icon) as the pattern input. It is literally then all or nothing > > > > > of whatever you pop into the Cull. If you need to have separate > > > > > streams that then process on after the switch then use multiple culls > > > > > and one switch linked to them all > > > > > > Jonathon > > > > > > On Mar 4, 11:09 am, PJ <[email protected]> wrote: > > > > > > > I do this a lot using a simple scripting component to intentionally > > > > > > 'break' chunks of the model. You just need a VB or C# component > > > > > > with > > > > > > the stream that you want to control and a boolean (or slider) as an > > > > > > input. Then just code in an if statement which checks if the > > > > > > boolean > > > > > > is true and if so outputs your stream. (Otherwise the output stream > > > > > > will be empty and anything that needs it as an input won't work). > > > > > > > Paul > > > > > > > On Mar 4, 3:05 am, JaH <[email protected]> wrote: > > > > > > > > Hello all, > > > > > > > > Does anyone have idea how could I make kind of switch which would > > > > > > > stop > > > > > > > or run certain part of the script. > > > > > > > My thing got really big and I am also doing few things in a > > > > > > > different > > > > > > > way , just to see the results, so i am afraid that it will become > > > > > > > too > > > > > > > heavy. I am keeping thing in Preview OFF but I believe that GH is > > > > > > > still doing the calculations behind... > > > > > > > Or the solution is good old manual dis/connecting? > > > > > > > > Thx > > > > > > > J- Hide quoted text - > > > > > > > - Show quoted text -
