I'm hitting this again… in order to stylize a widget I grouped it (by itself)
now we get to do the cool effects/inks to make it look good.
But it also is used as a button. and I place the group on all the cards in the
stack,
Now we have 3 different backgrounds all of which expect mouse events.
I can't any use case where you would want any group to trap a mouse event
outside its rect.
Seems only to introduce chaos. Especially where many custom controls may want
to be shared on multiple cards… it "goes crazy" and debugging the msg path and
hacking around this issue, starts to get nightmarish
BR
On 7/15/17, 5:46 AM, "use-livecode on behalf of J. Landman Gay via
use-livecode" <use-livecode-boun...@lists.runrev.com on behalf of
use-livecode@lists.runrev.com> wrote:
I saw this recently. It isn't a bug, the navigation group is a background
group so it will catch any message that isn't blocked earlier in the
message path. You can put an empty resizecontrol handler in objects that
shouldn't respond, or check in the group script that the target is one of
the group members, as you did.
_______________________________________________
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
