UI designers a bit ticked at OG5

[William Van Hecke]

Howdy Byron,

Thanks for taking the time to write this up! These are problems we've  
also run into ourselves, and have discussed around the coffee machine  
as recently as this morning. So I'll add your comments to the  
discussion, and hopefully we can improve the situation in a future  
update.

Thanks again,
William Van Hecke
~User Experience Lead~
The Omni Group


> OK, here are some particulars I recorded back in December - and lost  
> in the drafts pile, so apologies for not getting them in a lot  
> sooner!  These particular changes make my workflow much harder every  
> day than with OG4 pro:
>
> . I really miss the old way of indicating visible layers on the  
> canvas list - I find the disappearing eyeball very confusing when in  
> a hurry - I frequently misread the layer state & have to pore over  
> every layer in order to figure out which one is actually on & off.  
> Very painful when you have a multitude of layers (as I very often do).
> . I also miss the old "selected" indicator on the canvas list  
> indicating which layer a selected object lives in. Although the  
> abilility to select an object from the new object list is sometimes  
> helpful (when objects are totally occluded for example), it's not  
> nearly as useful as being able to select an object on the canvas and  
> quickly see which layer it belongs to. The selection is also not  
> actionable in the main view.  I used that a lot in OG 4 when  
> cleaning up misplaced objects, or moving objects to the proper layer.
>
> These new "features" are proving to be quite unproductive for me:
> . In OG 4 I could select an object, go to the canvas list, change  
> layer focus, and perform operations on the object like select  
> another  layer, duplicate the object into the new layer, nudge  
> around etc.  Now I find that although the object appears selected I  
> can't act on it. Instead I must go  back to the main window & then  
> de-select & re-select the object  - very difficult now! In many  
> cases the layer focus shifts to another layer (topmost?) - an action  
> whose rules I have yet to figure out & get it to perform consistently.
> . this "feature" also causes an impossible situation when attempting  
> to select underlying objects that are completely occluded - they  
> can't be manipulated, as hunting and then selecting them in the  
> object list and attempting to nudge (for example) only produces a  
> beep - no actions are possible without going back to the main view,  
> and finding a way to re-select the occluded object - kinda useless &  
> very frustrating :-).