If the mouseDown handler calls the mouseUp again, then it's a type of
recursion. You can avoid that by sending the mouseDown after the mouseUp
has ended :
if STOPP = 0 then
send "mouseDown" to btn "GO2" in 0
end if
(I wonder why your scripts lose all the spaces when they pass through the
list?)
How can one know how high one can set the recursionLimit before smoke,
sparks and flames are going to start leaping out of the back of the computer?
Usually there's no fire. LC just shuts down suddenly and you lose all your
work. After that, you set the computer on fire yourself. Ergo, the warning
and intercept.
On July 4, 2017 3:01:37 AM Richmond Mathewson via use-livecode
<use-livecode@lists.runrev.com> wrote:
Well I'm not doing infinite recursion:
MouseUp Script inside button "GO2" sending "mouseDown" to button "GO2"
onmouseUp
put0 intoSTOPP
ifintersect(img "ball1",img "stop") then
put1 intoSTOPP
endif
ifintersect(img "ball2",img "stop") then
put1 intoSTOPP
endif
ifintersect(img "ball3",img "stop") then
put1 intoSTOPP
endif
ifintersect(img "ball4",img "stop") then
put1 intoSTOPP
endif
ifSTOPP = 0 then
send"mouseDown" tobtn "GO2"
endif
endmouseUp
Richmond.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
