> On 17 Jul 2017, at 9:42 am, Sannyasin Brahmanathaswami via use-livecode
> wrote:
>
> I can't any use case where you would want any group to trap a mouse event
> outside its rect.
It sounds like you want sharedBehavior on and backgroundBehavior off
If it’s a
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
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
WE have a peculiar bug, at least I think it is a bug.
Where
1) navigation bar at bottom of screen, a custom control with a bkgnd grc 50 px
tall 1024 wide and 4 widgets on it.
2) has assigned behavior "behavior_bottomToolsNav"
# with some complex dynamic layout stuff happening to handle