|
you could do it thru script if you want more precision:
MoveOperatorBefore (strObject, strOperatorToMove, strOperatorReference)
MoveOperatorAfter (strObject, strOperatorToMove, strOperatorReference)
that will do it for you...
On 10/14/05, Andy Jones <andy(at)thefront.com> wrote:
This is not that big a deal, but does anyone else think the way the
construction mode reordering works is crazy? When I drag an operator
onto another, it gets placed above it in the stack. That would be fine
if it was just operators, but it's really counter-intuitive that if I
drag an operator onto a construction level, it gets placed in the
construction level above it. And to get something into an empty
modeling construction level, you have to do weird things like drag the
modeling construction level icon onto the operator. Because of the way
it's set up, it seems like it's often necessary to reorder operators in
two steps to get something back into the modeling stack. It shouldn't
be such a puzzle. Am I just missing something?
-Andy
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
|
