[Bf-committers] SVN commit: /data/svn/bf-blender [23184] trunk/blender/source/blender/ editors/mesh: after some discussion, this is the replacement for the old loopcut tool: edge ring select displays a preview of the edge ring, and you can move the mouse with ctrl-alt held down and change the edge ring selection .

[Roland Hess]

Joe wrote:

> after some discussion, this is the replacement for the old loopcut tool: 
 > edge ring select displays a preview of the edge ring, and you can move
 > the mouse with ctrl-alt held down and change the edge ring selection.

If this commit is just the first step on a road to a good solution, then
promptly ignore the rest of this. If not...

While this resolution might fit the internal code model for operators 
and MVC, it sure wreaks havoc with the UI guidelines.

Since when is it acceptable to have to actually hold down two modifier
keys plus a mouse button (with your weakest finger!) to do anything in
Blender? The previous loop cut solution was elegant from a user
standpoint. This one... doesn't even cut.

In my recollection, even having to hold down an unmodified mouse button
to push vertices around was bad (i.e. tweak mode), and to be avoided on
general grounds, plus to the prevention of RSIs.

Maybe we're stuck between two UI goals -- eliminate modals vs. no
"stress-based" tools.

Perhaps this level of UI discussion isn't appropriate at this time, but
loop cut is a huge tool, frequently used, and the statement in the
commit makes it seem like this is now the settled, agreed solution. It
doesn't have to be better than it used to be, but it sure can't be 
worse. I'm guessing the discussion about this happened either on IRC
or in person, but it would be great to have something like this "open"
so everyone can at least read the thinking that went into it so we
can understand the logic.

I'm not attempting to call Joe out in particular, but it would be cool
if anyone involved in this decision could try to explain it a little better.

Thanks
Roland
harkyman