The TAB menu is mostly typing based to access the operators you need. But the history of the TAB menu that shows the recently used operators are accessed using the mouse which is slower compared to typing IMO even with a tablet.
It would be very useful if we can invoke these via hotkeys by their order. So if you press 1 when the TAB menu is open, you invoke the last operator, 2 is the second from the last, and so on.
It could allow access up to 9 items (or 10 if you want to include 0) via hotkeys.
Since the TAB menu is probably one of the most frequently used item, any enhancement would improve the workflow tremendously. Here is a mock up I did showing how it might look like potentially:
Found 1553 posts.
Search results Show results as topic list.
Technical Discussion » USABILITY: Invoking last used OPs in TAB menu via hotkeys
- animatrix_
- 4515 posts
- Online
Technical Discussion » USABILITY: Show frame number being solved
- animatrix_
- 4515 posts
- Online
+1 from me as well. The frame number could also be placed at the start after elapsed time:
1:05 (frame 21) (Press ESC to cancel) Smoke_Dopnet …
1:05 (frame 21) (Press ESC to cancel) Smoke_Dopnet …
Technical Discussion » USABILITY: Details View to show current VOPSOP if not pinned
- animatrix_
- 4515 posts
- Online
I had to crop the title a little bit but I think this could be a very good enhancement.
It's very simple. As of now if you have a Details View that's pinned to a node, it always shows the attributes of that node. This is good. If it's not pinned, then it shows the currently selected node even if it's a VOPSOP, which is also good.
But if it's not pinned, and you go inside a VOPSOP, it shows nothing. IMO in this case, it should still show that VOPSOP being edited.
Why? Because:
1. It shows nothing otherwise which is no use when you have the Details View visible around the UI.
2. Personally I always needed to show the current VOPSOP that I am editing, but never complained about the other way around (i.e. showing something else) when not pinned.
3. If you want to accomplish this as of now, you go inside the VOPSOP, most of the time forget to pin the Details View, go back up, pin the view, then go back in.
So this pinning to show the VOPSOP while working inside it seems like something we shouldn't have to worry about.
I don't think this takes away control from the artist, as my suggestion is only when the Details View is not pinned.
Any opinions?
It's very simple. As of now if you have a Details View that's pinned to a node, it always shows the attributes of that node. This is good. If it's not pinned, then it shows the currently selected node even if it's a VOPSOP, which is also good.
But if it's not pinned, and you go inside a VOPSOP, it shows nothing. IMO in this case, it should still show that VOPSOP being edited.
Why? Because:
1. It shows nothing otherwise which is no use when you have the Details View visible around the UI.
2. Personally I always needed to show the current VOPSOP that I am editing, but never complained about the other way around (i.e. showing something else) when not pinned.
3. If you want to accomplish this as of now, you go inside the VOPSOP, most of the time forget to pin the Details View, go back up, pin the view, then go back in.
So this pinning to show the VOPSOP while working inside it seems like something we shouldn't have to worry about.
I don't think this takes away control from the artist, as my suggestion is only when the Details View is not pinned.
Any opinions?
Technical Discussion » USABILITY: Fit height to parameters for Parameters Window
- animatrix_
- 4515 posts
- Online
This is another small issue I noticed. I am talking about the Parameters Window, not the pane. When you right click a node and select “Parameters…”, it brings up a new Parameters Window which is immensely useful.
But I find this window to show up with either very small height, or way large height:
I think it would be pretty useful if this window was created to fit the parameters vertically on dialog create/open event just once, not dynamic. You would be free to resize it just like now after it's opened. The width can be anything.
Since it behaves a little unpredictable that I find myself always scaling the window for sure.
What do you guys think? Yay or nay?
But I find this window to show up with either very small height, or way large height:
I think it would be pretty useful if this window was created to fit the parameters vertically on dialog create/open event just once, not dynamic. You would be free to resize it just like now after it's opened. The width can be anything.
Since it behaves a little unpredictable that I find myself always scaling the window for sure.
What do you guys think? Yay or nay?
Technical Discussion » USABILITY: Turning off prefixes for parameters for assets
- animatrix_
- 4515 posts
- Online
Thank you Jeff. I really like discussing potential RFEs with the masters
Edited by - 2012年9月15日 10:53:13
Technical Discussion » USABILITY: Turning off prefixes for parameters for assets
- animatrix_
- 4515 posts
- Online
Does it save the asset settings too? I never thought it would. Have to try
Thanks Rob.
Thanks Rob.
Technical Discussion » A few usability suggestions...
- animatrix_
- 4515 posts
- Online
Thanks Jeff. How do you save the preferences? I tried Save Options as Defaults but it didn't seem to preserve my settings.
I created a new thread here per your suggestion:
http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&p=123733#123733 [sidefx.com]
Please feel free to continue discussing there
I created a new thread here per your suggestion:
http://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&p=123733#123733 [sidefx.com]
Please feel free to continue discussing there
Technical Discussion » USABILITY: Turning off prefixes for parameters for assets
- animatrix_
- 4515 posts
- Online
As per Jeff's recommendation, creating a new thread.
I have a small usability issue about these settings:
Personally I have never seen or made an asset that had prefixes which could be because the assets I used and made are not gigantic. I can understand the need for this for really big assets where there will be naming collisions, but I think they are in the minority.
IMO it would be pretty useful if these were turned off by default. If you want to make it even better, then when adding parameters, if Houdini realizes that there will be a naming collision from incoming parameters, then it could ask the user if he wants these settings to be turned on? If yes, then it would turn these on before adding the parameters. If not, then no parameter would be added.
EDIT: Another advantage to this would be to have shorter parameter names to use in expressions. SESI is smart to use short parameter names for operators, but if there were additional prefixes, then it negates the advantage IMO.
Also I wouldn't want to refer to “box7_testbed_size” to change size personally. A hand created “bedSize” or if it's the only size, then “size”, or “s” is much nicer I think.
I have a small usability issue about these settings:
Personally I have never seen or made an asset that had prefixes which could be because the assets I used and made are not gigantic. I can understand the need for this for really big assets where there will be naming collisions, but I think they are in the minority.
IMO it would be pretty useful if these were turned off by default. If you want to make it even better, then when adding parameters, if Houdini realizes that there will be a naming collision from incoming parameters, then it could ask the user if he wants these settings to be turned on? If yes, then it would turn these on before adding the parameters. If not, then no parameter would be added.
EDIT: Another advantage to this would be to have shorter parameter names to use in expressions. SESI is smart to use short parameter names for operators, but if there were additional prefixes, then it negates the advantage IMO.
Also I wouldn't want to refer to “box7_testbed_size” to change size personally. A hand created “bedSize” or if it's the only size, then “size”, or “s” is much nicer I think.
Technical Discussion » A few usability suggestions...
- animatrix_
- 4515 posts
- Online
Do we post them in this thread or post as a new thread?
I have a small usability issue about these settings:
Personally I have never seen or made an asset that had prefixes which could be because the assets I used and made are not gigantic. I can understand the need for this for really big assets where there will be naming collisions, but I think they are in the minority.
IMO it would be pretty useful if these were turned off by default. If you want to make it even better, then when adding parameters, if Houdini realizes that there will be a naming collision from incoming parameters, then it could ask the user if he wants these settings to be turned on? If yes, then it would turn these on before adding the parameters. If not, then no parameter would be added.
I have a small usability issue about these settings:
Personally I have never seen or made an asset that had prefixes which could be because the assets I used and made are not gigantic. I can understand the need for this for really big assets where there will be naming collisions, but I think they are in the minority.
IMO it would be pretty useful if these were turned off by default. If you want to make it even better, then when adding parameters, if Houdini realizes that there will be a naming collision from incoming parameters, then it could ask the user if he wants these settings to be turned on? If yes, then it would turn these on before adding the parameters. If not, then no parameter would be added.
The Orbolt Smart 3D Asset Store » Help cards
- animatrix_
- 4515 posts
- Online
SESI finally fixed the pasting issue, the MMB now uses a different clipboard I think. But copy paste to replace existing selection works. I never use the MMB pasting anyway
One thing that would really help is if we can select all text using Ctrl + A while in this tab. Ctrl + A works for parameter fields but not here, so the only workaround is to do these steps:
1. Alt + E to bring the extended editor
2. Copy
3. Go to the help tab of the asset you want to paste
4. Alt + to bring the extended editor
5. Paste
6. Save
7. Close the extended editor
Having this feature would be pretty sweet and save us 7 steps and make things more uniform across the board.
One thing that would really help is if we can select all text using Ctrl + A while in this tab. Ctrl + A works for parameter fields but not here, so the only workaround is to do these steps:
1. Alt + E to bring the extended editor
2. Copy
3. Go to the help tab of the asset you want to paste
4. Alt + to bring the extended editor
5. Paste
6. Save
7. Close the extended editor
Having this feature would be pretty sweet and save us 7 steps and make things more uniform across the board.
The Orbolt Smart 3D Asset Store » What are dependencies?
- animatrix_
- 4515 posts
- Online
AFAIK the purchase history doesn't carry over. Because if it did, then what if you want to charge for it? I am not sure though.
Update notifications should still work for the same assets. But it wouldn't notify Bend 1.0 users if you uploaded Bend 2.0.
Update notifications should still work for the same assets. But it wouldn't notify Bend 1.0 users if you uploaded Bend 2.0.
The Orbolt Smart 3D Asset Store » What are dependencies?
- animatrix_
- 4515 posts
- Online
From what I know, if you change the version of your OTL, the store will register it as a new asset. So all changes that you upload without changing the version will be stored in the same asset, where people will always download the latest version. Otherwise it's a brand new asset as far as the store is concerned.
Houdini Indie and Apprentice » Wacom Intuos 4 flips Y axis for a small period?
- animatrix_
- 4515 posts
- Online
Technical Discussion » UV transform centre pivot
- animatrix_
- 4515 posts
- Online
Houdini Lounge » Houdini 13 Wishlist.
- animatrix_
- 4515 posts
- Online
Houdini Lounge » Bold New Prices
- animatrix_
- 4515 posts
- Online
Sanostol, you might be running the wrong executable. I was trying to launch Houdini but soon realized, it was Houdini FX I had to run, not Houdini.
Houdini Lounge » Houdini 13 Wishlist.
- animatrix_
- 4515 posts
- Online
I agree with Rob. There are alot of small missing things that make the workflow less than optimal.
Technical Discussion » UV transform centre pivot
- animatrix_
- 4515 posts
- Online
I don't think there is. I asked for an RFE for this exact same thing recently. CEX, CEY, CEZ is only for geometry.
Houdini Indie and Apprentice » Wacom Intuos 4 flips Y axis for a small period?
- animatrix_
- 4515 posts
- Online
If it's wacom, then yeah let's send as many emails as possible. It's really frustrating. Not sure if all of us will amount to anything in the eyes of wacom though
Houdini Indie and Apprentice » Wacom Intuos 4 flips Y axis for a small period?
- animatrix_
- 4515 posts
- Online
-
- Quick Links