You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mouseChildren property within FlxMouseEventManager says that it disallows overlapping objects from receiving mouse events. However, this is only true when those overlapping objects were added to FlxMEM before the object with mouseChildren = false
Example: a sprite group is created and added, with mouseChildren = false. Its children are created and added. Clicking a child will result in both the parent and child receiving callbacks.
Possible solution: this behavior happens due to the unshift() within add(), but changing it to push() wouldn't fix the underlying issue. Perhaps sorting _registeredObjects, with the mouseChildren = false ones coming first, would work. unshift if it's false, push if it's true, and sort/rearrange if setObjectMouseChildren is called.
When two overlapping objects have mouseChildren disabled, it's unclear what should happen.
The text was updated successfully, but these errors were encountered:
The
mouseChildren
property withinFlxMouseEventManager
says that it disallows overlapping objects from receiving mouse events. However, this is only true when those overlapping objects were added toFlxMEM
before the object withmouseChildren = false
Example: a sprite group is created and added, with
mouseChildren = false
. Its children are created and added. Clicking a child will result in both the parent and child receiving callbacks.Possible solution: this behavior happens due to the
unshift()
withinadd()
, but changing it topush()
wouldn't fix the underlying issue. Perhaps sorting_registeredObjects
, with themouseChildren = false
ones coming first, would work.unshift
if it's false,push
if it's true, and sort/rearrange ifsetObjectMouseChildren
is called.When two overlapping objects have
mouseChildren
disabled, it's unclear what should happen.The text was updated successfully, but these errors were encountered: