I take that back, the card group shouldn't get the message. Sounds like
something else is wrong.
On 12/8/19 5:24 PM, J. Landman Gay via use-livecode wrote:
Is the group that receives the mouseUp a card group or a background
group? If I remember right, messages go from the button, to all card
groups, then to the card, then all background groups, then to the stack.
So if it's a card group, it will get the message before the stack does.
On 12/8/19 1:55 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
I think this a old problem that is re-surfacing. Or else it is known….
9.6 dp1, in the message path different independent groups are not
encapsulated.
button "starWidget"
-- has no script
-- is not a part of any group
Stack script:
on mouseup
put the short name of the target
put the short name of the target into tTarget
switch tTarget
case(s) # various button names
# consolidate all UI actions that not part of a group
# to the stack script
end switch
end mouseup
# the card are several groups,
# each with its own mouse handlers
# I click on button "starWidget"
-- nothing happens…hmm, no errors either…
# start profiling scripts (new trick I found)
# click on button "starWidget"
# stop profiling scripts:
# Voila! the mouseup was trapped by one the other groups,
as if they were in the message path.
Is there any way around this? Meanwhile I have to plug into every
button explicit handlers. Tedious, make debugging painful…
BR
_______________________________________________
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
--
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
