Control Ids & Ordinals of Cloned Stacks

xbury.cs at clearstream.com xbury.cs at clearstream.com
Tue Dec 2 10:10:21 EST 2003


Rob,

try the old finder duplicate file feature! 
Just remember that RR or MC can't handle two stacks with the same name! 

--
So many limits and just one lifetime to bust them!
---------------------=---------------------
Xavier Bury
TNS NT LAN Server
ext 6465




Rob Cozens <rcozens at pon.net>
Sent by: use-revolution-bounces at lists.runrev.com
02/12/03 15:04
Please respond to How to use Revolution

 
        To:     How to use Revolution <use-revolution at lists.runrev.com>
        cc: 
        Subject:        Control Ids & Ordinals of Cloned Stacks

.


Hi All,

Yesterday I was surprised to find that the ids & ordinals of the menu 
buttons and other controls of a cloned stack were not the same as 
those in the stack it was cloned from.  (At least not always, if it 
seems to work for you, try modifying the order of the controls in the 
source stack before cloning it.)

Apparently, if one uses control id references in stack handlers, one 
must be sure never to clone the stack.

I reference menu buttons by id rather than name to support 
application translatability.  I have had to change the references 
from "button id [the id]" to "button [ordinal] of group "myMenubar" 
in stacks that can be cloned (plain "button [ordinal]" also resolves 
to different controls in the original & cloned stacks).

It seems to me that, ideally, a cloned stack should be identical to 
the stack from which it was cloned.  If you are expecting this 
behavior, be aware it isn't always so.

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.net/who.htm

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)
_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution





Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.

The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.

END OF DISCLAIMER


More information about the use-livecode mailing list