Setting the icon of a btn on preOpenStack

Bob Sneidar bobs at twft.com
Tue Jun 22 14:31:20 CDT 2010


Even better Jacque. Methinks it's wise to keep handlers local to the objects being worked with, or their parents at the highest. That way your code is easier to find at a later time. 

Bob


On Jun 22, 2010, at 9:47 AM, J. Landman Gay wrote:

> Bob Sneidar wrote:
>> Too little information. Where is the pre-openstack handler? Is it in
>> the substack? Are you opening the substack to fire this handler?
>> Secondly, I am not sure you can refer to an object in an as yet
>> unopened stack. It's not open yet, see? But what you can do is set
>> the lockscreen to true in your preopenstack handler, then put your
>> button icon settings in your opencard handler for the card that
>> contains the buttons. The screen will remain locked until all the
>> scripts have finished running (if I am not mistaken).
> 
> That was my first thought too. Or he could just move the icon assignments to a preOpenCard handler on the first card. That triggers before the user sees the stack and no lockscreen would be necessary.
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list