With that said wouldn't proper way of settings things up be to give it and test on number of people that will actually be the ones using tool and see what they say :)
If programmer making something for artists shouldn't that follow what artists needs not what programmer feels it should be ;) On Fri, Feb 20, 2015 at 6:20 PM, Luc-Eric Rousseau <[email protected]> wrote: > Hello I know what you're saying, but the way I saw it, those scenarios > were "select the many, and then highlight the one". This allows you > to select everything and then highlight the "target" for example the > motion path or the parent, and the UI supports that paradigm with the > green highlight of The One. > > Thinking in terms of source and target is not always unambiguous in > UI. For example, if you have a menu that applies a LookAt constraint, > what's the "target", is it what the object will end up look at, or > what the object the menu command acts upon. A technical individual > might see things as picking all the inputs of an operator and then the > output, and an artistic person might see things differently and read > it like subject/verb/object. > > On Fri, Feb 20, 2015 at 1:11 AM, Ponthieux, Joseph G. > (LARC-E1A)[LITES] <[email protected]> wrote: > > I think you've missed my point. Some of Maya's selection context is done > in a normal or intuitive manner. Others are not. The point is that Maya's > selection contexts are all over the place and the fact that some processes > bear out multiple contexts only confuses matters. In the case of parenting, > Maya gets the natural selection order right with the target being last. Its > the majority of other processes that are unintuitive and inconsistent with > this one. > > > > I fail to understand how having to read the status line everytime i > parent, constrain, or path animate something might be intuitive. > > > > I've been using using Maya since 98. I know where to get the status line > information. I've written MEL scripts that post status line instructions. > Thats not the point. > > > > The point is that the selection methodology in Maya is inconsistent, > incongruent, and unintuitive. As if though each process was written by a > different person at a different time and nobody knew what the other person > was doing. This incongruency demonstrates that Maya completely ignores how > and why we as users, as humans, think when it comes directionality of > source -> target and how percieve this concept. > > > > This should be a simple intuitive process that the user can instantly > extrapolate without having to read the manual every time you switch from > parenting to constraints or animating. This is selection methodology. We do > this one task, select items, hundreds of times a day. And Maya has no > uniform selection paradigm. In fact Attach to Motion Path can even mislead > the user into adopting bad behavior by allowing the user to think the > selection order is one way until you go to motion path one curve on another > and then it can be opposite the way someone has earned to attach objects to > a curve. This is illogical. > > > > The original poster has a valid and salient point. And its not enough > that all contexts are the same. They could all be the same and still be > unintuitive because they could be contradictory to the way we think about > selection naturally. Selection has to be designed to the way we as humans > think and not just a procedure for the sake of being a procedure. > > > > From: Luc-Eric Rousseau [[email protected]] > > > > On Thu, Feb 19, 2015 at 2:23 PM, Ponthieux, Joseph G. > > (LARC-E1A)[LITES] <[email protected]> wrote: > >> (as already noted by another poster) > >> > >> If you have two primitives selected, and attempt to parent constrain, > the > >> second selected object will constrain to the first > >> > >> (as already noted by another poster) > >> > >> If you have two primitives selected, and attempt to parent, the first > >> selected object will become child of the second > > > > isn't this because you'd select all the children you want to parent, > > and then finish with the single parent, > > or select all the object you want to parent-constraint to, and then > > finish the single target? > > The "single" object is always last and highlighted in green vs other > > ones in white. > > > > > > btw, it's written on the help line at the bottom of the screen what > > you need to select to run the menu command: > > Parent: "Parent the selected object(s) to the last selected object" > > Contraint->Parent: "Select one or more target followed by the object > > to constrain" > > > >
