First, why are you locking messages when you go to a card? Second, sending a mouseUp to a button does not click the button. It only runs the mouseUp handler contained in that button. If you have a mouseUp handler, then you will need to pass mouseUp in order for the engine to properly check the box.
But a better way would be to set the hilite of the button to false. I'm still leery about whether the card and it's objects get loaded in memory properly if lock messages is true. I'm a little sketchy here. Bob On Nov 4, 2010, at 2:28 PM, charles61 wrote: > > I am trying to use the following in another handler to send a mouseUp to > hilited checkboxes on marked cards but it does not work. Any suggestions? > > on doStuff3 > put the num of this card into tStartCard > lock screen > repeat with y = 1 to the number of cards > if the mark of card y <> true then > next repeat > end if > lock messages > go card y > unlock messages > repeat with b = 1 to the number of buttons > if the style of button b = "checkbox" then > if the hilite of button b = true then > send "mouseUp" to button b > end if > end if > end repeat > end repeat > lock messages > go card tStartCard > unlock messages > unlock screen > end doStuff3 > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/What-is-wrong-with-this-script-tp3027821p3027821.html > Sent from the Revolution - User mailing list archive at Nabble.com. > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
