Thomas McGrath III wrote:
Jac, but once you get to the second stack with the pointer tool the
selection is lost? No? I have to play some more. I was just hoping for
experience.
I tried a quick experiment before I answered and the selection stays
until you select something else or click in a n
to act on a user selected object in stack one while in stack
two.
I'm not seeing any problem with just using "the selectedObject". It
returns the long name of the object that's selected with the pointer
tool regardless of what stack it's in.
--
Jacqu
setting the defaultStack to stack1 before referencing the
selectedObject? (This is a guess, but seems plausible)
Phil Davis
Thomas McGrath III wrote:
Is there a way that I am missing to get a selected object from one
stack in another stack 'without' having to palette the window of
Humpf:
probably have to set the DEFAULTSTACK to the stack which you are wishing
to act on, select the object, manipulate, and then set DEFAULTSTACK back
to the stack from which the manipulation command is coming.
Probably best to set the LOCKSCREEN to true while you do this so as
to avoid problem
with just using "the selectedObject". It
returns the long name of the object that's selected with the pointer
tool regardless of what stack it's in.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
How about setting the defaultStack to stack1 before referencing the
selectedObject? (This is a guess, but seems plausible)
Phil Davis
Thomas McGrath III wrote:
Is there a way that I am missing to get a selected object from one
stack in another stack 'without' having to palette the
Is there a way that I am missing to get a selected object from one
stack in another stack 'without' having to palette the window of the
second stack?
I want to act on a user selected object in stack one while in stack two.
Thanks
Tom McGrath III
Lazy River Software
3mcgr...@comcast.net
iTu
On 25 Oct 2005, at 05:54, Jerry Daniels wrote:
David,
I am having trouble with the concept of selecting something without
the user touching it. We could, of course, make a preference for
this behavior.
? That is the behaviour of Constellation no - select in object
browser and manipulate
David,
I am having trouble with the concept of selecting something without
the user touching it. We could, of course, make a preference for this
behavior.
Best,
Jerry
P.S. I hope you get treatment for that virus, too.
On Oct 20, 2005, at 2:42 PM, David Bovill wrote:
On 20 Oct 2005, at
On 20 Oct 2005, at 19:39, Jerry Daniels wrote:
We USED TO select the object during no-click inspection--if the
pointer was chosen.
Recent version changed this right - kindo of liked it myself - now
I'm still stuck as i cant
1. The TITLE of Constellation's window has the full name of
David,
First of all, the feature "no-click" inspection is a feature of
Inspection Gadget which works with either Constellation OR the Rev
script/prop editors.
We USED TO select the object during no-click inspection--if the
pointer was chosen.
However: that became problematic because the
Like the fact you can work with objects without actually selecting
themn but how can you determine which object is "selected" from
constellation from a script? In a bit of a consternation over this?
___
use-revolution mailing list
use-revolution@
12 matches
Mail list logo
