Max,

I tried w/ 3d boxes earlier. They do not move, other items are moved to the 3d boxes position one by one.

On Dec 29, 2009 10:52 AM, "Maximilian Albert" <maximilian.albert@googlemail.com> wrote:

Hi,

disclaimer: I haven't looked at the patch yet. Just a few random
thoughts coming to mind:

2009/12/29 Roland Meub <roland.meub@gmx.de>:

> Just a few words to clarify the logic behind the rotation order: > The current implementation exch...

So what is the order when the user selects the objects by drawing a
rubberband around them, or by using "Select All" (Ctrl+A)? I suppose
that it is predictable, but is it transparent to the user? And does it
result in the behaviour the user expects (whatever that may be)? I
think that the current behaviour is useful, but it's potentially
dangerous to assume that it is always what the user wants.

> This brings me to the question whether we should really try to implement a > strict (for example ...

One option would be to break ties by taking z-order into account. Or
to move those objects as if they were a single object. But what does
'located at the same X' position mean anyway? When looking at the left
border, the right border, the rotation center, ...? Just a few points
to consider.

Max

P.S.: The issues you encountered with 3D boxes are indeed not caused
by your code. Maybe they are already fixed by my recent commits.
Otherwise I will take a look at them soon-ish.

------------------------------------------------------------------------------ This SF.Net email is...