Hi, I'm sending this as an RFE, but figured that I could also post it here in case any other guys/gals wanted to add other improvements for the TAB Menu.
1. Add Recent History Numbering.
- Currently, when pressing the TAB Menu, the recent ones are shown below. It would be great if those are numbered sequentially. Then a user could just press a number corresponding to the node on the history list to create it.
2. Show HDAs
- The nodes that appear on the TAB menu is currently a mixture of both built-in nodes and HDA's. It would be great to have a way for users to be able to differentiate default one's and HDA ones.
Here are a couple of suggestions to differentiate HDAs:
a. HDAs could be colored differently.
b. HDAs could be italicized.
c. HDAs could have a small locked icon displayed at the end of its name.
d. HDAs could simply have an * (asterisk) at the end of its name.
3. Retain Categories
- Upon opening the TAB Menu, as we type letters like “po”, we get a mixture of nodes that are from “Attribute”, “Polygon”, “VDB”, “Utility”, etc.. It would be great if the results could also display the category that the node belongs to.
Cheers,
Jeff
TAB Menu Improvements
2842 3 1-
- galagast
- Member
- 267 posts
- Joined:
- Offline
-
- pezetko
- Member
- 392 posts
- Joined: Nov. 2008
- Offline
1. Like that, nice idea
Could you please post its RFE number?
2. A lot of internal built-in nodes are HDAs too. Do you want to differentiate between black-boxed/C++ nodes and opened (HDAs) nodes? Or between built-in and your/(third party) custom HDAs?
3. I though that when you are typing you usually know what are you going after. This could potentially make the filtered list much bigger then it has to be.
Could you please post its RFE number?2. A lot of internal built-in nodes are HDAs too. Do you want to differentiate between black-boxed/C++ nodes and opened (HDAs) nodes? Or between built-in and your/(third party) custom HDAs?
3. I though that when you are typing you usually know what are you going after. This could potentially make the filtered list much bigger then it has to be.
-
- galagast
- Member
- 267 posts
- Joined:
- Offline
1. I haven't got an RFE number yet. But I did send the mail yesterday. I'll post the RFE here as soon as I receive it.
2. That would also be neat. Differentiate between these:
A. Black-Boxed/C++ Nodes
B. Built-in HDAs
c. Third Party HDAs
Although initially, I'm ok with just (A) and (B).
3. I agree, although I can recall back when I was starting, most of the tutorials I've seen, the tutors tend to just type the node name (and not go through the categories). Having categories visible could help new users have a hint what nodes are for based on the category name.
In order to avoid creating a very big list due to category names, maybe those can be listed on the right hand side of the node name. Something similar to this (Magma's activetype):
2. That would also be neat. Differentiate between these:
A. Black-Boxed/C++ Nodes
B. Built-in HDAs
c. Third Party HDAs
Although initially, I'm ok with just (A) and (B).

3. I agree, although I can recall back when I was starting, most of the tutorials I've seen, the tutors tend to just type the node name (and not go through the categories). Having categories visible could help new users have a hint what nodes are for based on the category name.
In order to avoid creating a very big list due to category names, maybe those can be listed on the right hand side of the node name. Something similar to this (Magma's activetype):
Edited by galagast - March 4, 2017 20:17:10
-
- galagast
- Member
- 267 posts
- Joined:
- Offline
-
- Quick Links

