Now we have A:
a b c d e f g h i j k l m
What I am suggesting is B:
a f j b g k c h l d i m e
Alphabetical order of attributes in the Node Info
796 7 2
-
- ikoon
- Member
- 202 posts
- Joined: Jan. 2016
- Offline
-
- Enivob
- Member
- 2610 posts
- Joined: June 2008
- Offline
-
- animatrix_
- Member
- 4621 posts
- Joined: Feb. 2012
- Offline
ikoon
This is not a bug. But wouldn't it be better to have the attributes listed alphabetically below each other?
Now we have A:a b c d e f g h i j k l m
What I am suggesting is B:a f j b g k c h l d i m e
That's a cool idea!
Senior FX TD @ Industrial Light & Magic
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
Get to the NEXT level in Houdini & VEX with Pragmatic VEX! [www.pragmatic-vfx.com]
youtube.com/@pragmaticvfx | patreon.com/animatrix | pragmaticvfx.gumroad.com
-
- mchaput
- Staff
- 500 posts
- Joined: July 2005
- Offline
ikoon
This is not a bug. But wouldn't it be better to have the attributes listed alphabetically below each other?
The problem is when there's too many attributes to fit in the window and you have to scroll. Then you only see the tops of the alphabetized columns, with the rest hidden below the scrolling view, so like:
A M X
B N Y
C O Z
D P
...which is a bit confusing. (Or, you make the attributes view scroll horizontally, which I don't think would go down well
)
Edited by mchaput - July 29, 2024 16:24:24
-
- ikoon
- Member
- 202 posts
- Joined: Jan. 2016
- Offline
@mchaput Thank you very much for working on the new Node Info. I like it very much!
As regards sorting, thank you for considering it. I have to admit that I often look for the right attribute a bit "mindlessly". I automatically skim through the list with my eyes, while thinking about the problem I am solving ... and the item "pops" under my eye.
So, for the "mindless" or "effortless" search, I believe that B is better. It is easier to skim through the first characters in a column. If I "shoot" my eye into the B list, I know whether to go up or down. If I shoot my eye into the A list, I cannot iterate easily.
The root of the problem might be the distance between columns which makes it difficult to read them as lines.
I feel like in this worst case scenario, I might be lost once, or twice (between columns):
But with this, I am bit lost on each item:
I opened this thread because sincerely I am not sure that I am right. Maybe I have to get used to the better solution (which certainly happens often).
As regards sorting, thank you for considering it. I have to admit that I often look for the right attribute a bit "mindlessly". I automatically skim through the list with my eyes, while thinking about the problem I am solving ... and the item "pops" under my eye.
So, for the "mindless" or "effortless" search, I believe that B is better. It is easier to skim through the first characters in a column. If I "shoot" my eye into the B list, I know whether to go up or down. If I shoot my eye into the A list, I cannot iterate easily.
The root of the problem might be the distance between columns which makes it difficult to read them as lines.
I feel like in this worst case scenario, I might be lost once, or twice (between columns):
A M X
B N Y
C O Z
D P
But with this, I am bit lost on each item:
Alpha b_guide b_prevnode_dir
b_prevnode_length b_result b_result_length
b_step Cd centerline
centerline cluster dim
guide mask objid_crop
P range_end range_start
skinprim skinprimuv skinqueryP
u
I opened this thread because sincerely I am not sure that I am right. Maybe I have to get used to the better solution (which certainly happens often).
-
- ikoon
- Member
- 202 posts
- Joined: Jan. 2016
- Offline
With those columns having such a margin between them, my eyes "effortlessly" just snap to the closest word (up or down a line) and brain can't deal with it. But maybe it is just me.
Sorry for the rambling, I believe that it (or I
) will mature into the perfectly usable Node Info!!! Thanks for the efforts!
Alpha b_guide b_prevnode_dir
b_prevnode_length b_result b_result_length
b_step Cd centerline
centerline cluster dim
guide mask objid_crop
P range_end range_start
skinprim skinprimuv skinqueryP
u
Sorry for the rambling, I believe that it (or I
) will mature into the perfectly usable Node Info!!! Thanks for the efforts!
-
- ikoon
- Member
- 202 posts
- Joined: Jan. 2016
- Offline
-
- mchaput
- Staff
- 500 posts
- Joined: July 2005
- Offline
-
- Quick Links