PDA

View Full Version : Compiled list of redundant keypresses that should be eliminated



jeric_synergy
08-13-2015, 10:18 PM
Redundant keypresses , clicks, and unneeded mouse navigation add to user fatigue.

The devs aren't animators, they don't necessarily experience which actions are wasting animators' time and motion. This is a catch-all for those things as they occur to you.

Here's 5 for starters:
+++++++++++
Clicking on the SEARCH BOX in the Key & Menu Editors -- unneeded. Should be active and ready to go as soon as the panel appears.

Turning OFF "Keep 1-point Polygons" in MERGE POINTS. Every. Damn. Session.

In the LWM Layers Panel, 'twirling down' the little triangle so you can actually see the layers.

Having to click the EDIT button in BUILD NULL OBJECT in Layout.

Having to turn on the Colors in BUILD NULL OBJECT in Layout.

Kryslin
08-14-2015, 11:18 PM
The last two can be taken care of by using my Build Null Object 2.0 script, available somewhere in this very topic!

Number 2 sounds like someone forgot to put a recall/store call for some of the interface for merge points...

erikals
08-15-2015, 12:03 AM
for Merge, use this plugin > Merge Points NR
https://www.lightwave3d.com/assets/plugins/entry/merge-points-no-requester

jeric_synergy
08-15-2015, 12:06 AM
Guys, this isn't about 3rd party solutions, it's about LW3dG getting informed about where they are making extraneous work for their users.

jeric_synergy
08-18-2015, 09:04 PM
OPENING the only darn object in Modeler in the Layers Panel. Pointless labor. Should default to OPEN.

jeric_synergy
08-24-2015, 11:58 AM
In Layout, in the Object Properties/FX tab, when you hit CALCULATE the numeric UI at the bottom of the panel closes. Pointlessly.

This just forces the user to click on that FX again.

Again, another useless click. WHY?

jeric_synergy
08-24-2015, 02:44 PM
When examining a point's UV coordinates in the INFO panel, altering a point's UVs causes the texture display to "collapse", requiring the user to manually open it again.

This seems burdensome: if the code can COLLAPSE the texture display, surely it can RE-open it too, as the user desired.