iaminnocent wrote:Plus, that dashed line really reminds me of a crotch for a design that needed to be replaced, not brought back.
I agree that this dashed line is not the most aestethic thing, but it could be easily made more attractive with a dot at the end.
I wasn't using the word 'crotch' to refer to its appearance. I meant to say that if the motion based system of old times was working well, it wouldn't need to be assisted by the dashed line. But keep reading on : I'm coming around to see your point better.
But i have to say that i never see that line.
I am guessing that you probably use just a quick click of MMB. Then the dashed line only flashes on the screen and is barely noticeable (or of any use for that matter, but only then)
I just make a small move of 5pixels in the right direction, and it feels just like a click on the mmb. If you take the time to see where is your dotted line, i think that you didn't catched the purpose of this system : speed. Just use it as it were a mouse gesture with mmb !
Ummm... I don't know Efbie : if the purpose was to use it just as the old system why then change anything ? My understanding from reading http://projects.blender.org/pipermail/t ... 01081.html
was that the new system aimed at fixing a problem mainly for those like me who almost never works in any other view than perspective. MMB gesture just isn't doing it for me under some viewing angles. 90% success is still 10% frustration and makes for a long day's work.
But, thanks to your comments
, I begin to understand why the motion base system was brought back in and I agree that it speeds up the work when MMB flashing is usable.
Nevertheless I can use it just about as easily as I was able when the proximity of the pointer to an axis was determining the constraint. There is one caveat though : the mouse pointer is better to be close to the center of the object when one starts the transformation for the motion base choice to work well. If the pointer is offset somewhat or more, it has to remain that far from the temporary axes' origin for a choice to be possible. I can feel a lot of the same beginner's question coming on that point. IMO, if this were to be the case, then it would be just one more sign that the old desing always was a bit flawed.
the motion is totally indpendant from your inital mouse position. I never had a problem with it.
I tried it again and it's definitely there.
It may be (probably is) because you are an MMB flasher only : if you had to hold the MMB for a long time, which is the only way to consistenly choose the right axis in some extreme perspective views, when two of the axes makes a very acute angle on the screen for example, then you'd see that behavior too.
All in all, I can live with it but I'm pretty sure that most people and I would live better with the proximity design.
I think that the people who want to use a easy and not so fast system can use the widget. Thoses who wants a fast and effective system can use the "gesture" one.
I hope that I explained my point well enough for you to understand that it is not just a question of ease : under some view angle it is downright unpractical to use MMB flashing, if possible at all.
BTW, I think that the new widget itself is only meant for local transforms, something MMB flashing won't do any way I know of (but I am willing to learn
I understand your point. That just won't work for me or for other for whose selection problems the reform was designed to solve. The way I use it is still pretty fast, faster than using the keyboard shortcuts ; it's just not 'lightning fast' and I still can get used to MMB flashing when the angle of view is not too extreme.
Thanks Efbie : through it all I found some clarification of why the motion base system was brought back and, since I can live with it, I think that it just might be the best compromise between users like you and me.