So I get the feeling that you don't think a visual cue is a good idea?
On Jan 27, 4:38 am, David Rutten <[email protected]> wrote: > The main purpose of the "Extract Parameter" feature is that local data > stored inside input parameters cannot be shared with anyone else. If > you've spend half an hour selecting 250 curves in the correct order > for a Loft operation, you'd probably like a way to duplicate that data > into a free-floating parameter so it can be separated from the Loft > Component logic. > > -- > David Rutten > [email protected] > Robert McNeel & Associates > > On Jan 26, 7:59 pm, opposablethumbs <[email protected]> wrote: > > > Hello David, > > > The reason I thought it would be nice is that I find myself using a > > lot of components that are unnecessary because they could be assigned > > to an input via right click. > > After reading Fraguada's reply and yours I think I understand a dual > > purpose of using "extract parameter" in that if I assign a value via > > right click I can extract that parameter as a component to visually > > cue me that there is in fact an input going into the component. But > > like you said, expression aren't able to do this. > > > Since I'm a novice I tend to over document definitions so I know > > what's doing what, I was thinking that this could help. > > Thanks for reading. > > > On Jan 26, 1:34 pm, David Rutten <[email protected]> wrote: > > > > I can see the point of having a special display for expressions. But > > > you can tell that a parameter gets data from elsewhere if there's a > > > connecting wire. If there's not, the data is local. What more visual > > > feedback could you need? > > > > -- > > > David Rutten > > > [email protected] > > > Robert McNeel & Associates > > > > On Jan 26, 5:33 pm, fraguada <[email protected]> wrote: > > > > > I am not sure if it would be along similar lines, but perhaps the same > > > > thing if a value is being edited by an expression...the input somehow > > > > highlights...yeah, minor wish on my part as well... > > > > luis > > > > > On Jan 26, 4:52 pm, opposablethumbs <[email protected]> wrote: > > > > > > Hey David, > > > > > > I'm not sure if this would be welcomed by all, but I was curious if > > > > > you ever thought to somehow visually change a component's input that > > > > > has a value assigned locally. > > > > > > For example, if you have a component and instead of having another > > > > > component feeding into it's input you have assigned it by right > > > > > clicking the input and entering a value you could either have the text > > > > > go bold, or change the color of the connector. > > > > > > I hope this makes sense. > > > > > Thanks.
