I'm not sure you can do this with the existing modules. The problem with just applying the transform is that the transform doesn't end up in the object at the appropriate place to be understood as a transformation to the screen object position. If you do a print of the output of colorbar, you'll see that at the top level it's a screen object. *THEN* you see a transformation matrix which indicates its position (the default shows an offset of .95 .95, which is in screen coordinates). I don't know of a way to modify this transformation matrix inside the screen object (other than writing a module).
So I guess I wonder why not just do it at the level of calling colorbar, by modifying the "position" input (as someone suggested)? _________________________________ Donna L. Gresh, Ph.D. Visual Analysis Group IBM T.J. Watson Research Center (914) 784-5049 [EMAIL PROTECTED] "Sharon Cady" <[EMAIL PROTECTED]>@opendx.watson.ibm.com on 10/24/2000 03:44:52 PM Please respond to [email protected] Sent by: [EMAIL PROTECTED] To: [email protected] cc: Subject: Re: [opendx-users] moving a screen object (colorbar) Do I have to do something else to make the translation show up on an image with other elements ? Although the colorbar is now Described as a "translated object", it has not visibly moved. I am piping the translated object into a Collect and then feeding it into Image with a Camera. I don't know if this detail is pertinent, but one of the other image elements is an Arranged object. Also, I don't know what units the translation is in (pixels ? page normalized units, like the original colorbar ?) but there seems to be no effect whatever value I enter.
