Dave wrote:
Sounds a lot like the GM to me. It handles a lot of basic
situations well.
Yes, but at the drop of a hat it goes Beswick!
That may not be merely a limitation of the GM, but possibly a bug. Did
you report it? It'd be interesting to run the sample stack submitted
with the report to find how it could be repaired.
There are three main ways to refer to objects with Rev: ordinal
number, name, or ID.
...
Which of these three ways to refer to objects do you use?
None of them! I set a "listen" (Based on a MessageID and MessageKind)
in the object that wants to get the message, then I just send to this
MessageID and MessageKind. The object receives the message, and,
since it's running in the object's script, can use "me".
I think I may be slow this morning, as I'm not following this method.
The resizeStack message is sent to the card, not the controls on the
card. So how do these controls get notification to update themselve
without something referring to them without using one of the three ways
to refer to objects?
That way I can copy objects around, dupe them, whatever and other
parts of the stack(s) don't break!
If the resizeStack handlers are replicated in the objects themselves,
how do you handle situations like my example, where some object
positions are determined by others?
And in such a case, how would the object whose position is dependent on
another know the other object's position without referring to it?
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
