0.7.x Expression Hint Wish

Hola,
I like the expression hint asterisk on the modified input:

I was wondering if it would be too much of a PITA to add something like this:

Ok, so how to handle lists/trees?

Maybe in general a line could be added to the top of the list...some thing like:

10 values inherited from 1 source

Expression: Abs(A)

1

2

3

4

5

Apologies in advance for my use of MS Paint.

Replies to This Discussion

Permalink Reply by taz on May 21, 2010 at 8:08pm

Hmm... Interesting.

I think I like the text based idea since sometimes expressions can get a bit muddled and long.

Permalink Reply by David Rutten on May 22, 2010 at 2:27am

I like that. I'll get right on it after my holiday's over.

--
David Rutten
david@mcneel.com
London, UK

Permalink Reply by FrankS on May 25, 2010 at 1:49am

additionally, can we get a subtile hint for a numerical value hard-coded in an input?

if asteriks is reserved for expressions, then maybe "°" (if this is not too confusing since normally refering to degrees...)

Permalink Reply by David Rutten on June 4, 2010 at 7:17am

Frank,

since this is such a common case I'd rather not add symbols to the interface to indicate it.
An empty input parameter will result in an orange component, and the tooltips can be used to quickly examine local values.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by FrankS on June 6, 2010 at 1:15pm

david,

i do understand your intention to keep the interface clean. it's just that i sometimes experience difficulties teaching GH to students when there are "hidden switches" involved. students cannot achieve the same result as in the projection, because there is something invisible still essential inside the definition. same it true for screenshots on this forum.

maybe there could be an optional display mode that adds information for "hidden parameters" (similar to "profiler" or "draw icons" modes)

the following i percieve as hidden parameters:
- reparametrize
- flatten
- shortest, longest, cross-reference
- numerical values ( int, floats, domains,...)
- booleans
- expressions

if all these information is to much for the canvas, maybe the information could only display on selected components.
the existing mouse-over-tooltip-method is too single-focus IMO.

what do you think?

cheers,
frank

Permalink Reply by David Rutten on June 6, 2010 at 2:33pm

I'm not sure yet what I think. I'll need some more time.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by FrankS on June 6, 2010 at 3:00pm

well, i have to admit that i am not fully aware of the consequences nor do i have a clear image of the implementation.
but i like visual hints on every detail in a definition, somehow. will sleep on this one...

thanks for considering!

anyway core functionality comes first...

RSS