Method for Getting MouseDown on TopMost Object Only

#1 If you have any objects receiving mouseDowns because they have "mouse lock" on, these objects will get the mouseDown first, even if they are in a higher-numbered layer (lower layer) than other objects under the mouse. I don't have a TorqueScript solution for this.

To solve this, I'd propose a future version of T2D could either send mouseLock objects their events AFTER the unlocked objects. Or, even better, sort the locked objects into appropriate order along with the layered objects.

Note that the above fixes (either one of the two) would also solve a bug where you sometimes get two events while unlocking the mouse. For instance, you first receive the mouseDown due to being locked. Let's suppose your callback unlocks the mouse. Then, T2D calls all objects that are actually under the mouse. At this point, T2D tries to skip objects that are locked but under the mouse, because they've already been called. However, you just unlocked the mouse, so you receive the event again.

#2 Started implementing this to fix an issue and it works pretty well :)

Though, the second part is:

function t2dSceneGraph::onUpdateSceneTick(%this)
{
if ($mouseDownEaten) {
$mouseDownEaten = "";
}
}

#3 Guys you want to block mouse evens for sprites below, so when you click on the top most object all beneath ones were not receiving the click, am I correct?
you can do something like:

function topSprite::onMouseEnter(blabla)  
    {  
    belowSprite.setUseMouseEvents(false);  
    }

But a better way would be to modify the source and save tons of time, here is the link
www.garagegames.com/community/blogs/view/19719
There are also other ways there of doing it through script.

#4 Hi @Harry,

Hope your problems are solved!

You can give your t2dSceneGraph a name and use it specifically. In my case I used MySceneGraph. I agree that was a bit confusing. Thanks for the pointer.

Now if you are feeling like updating some C++ and you have more complicated situations where you want to get only one mouse call, I wrote this patch: http://www.garagegames.com/community/forums/viewthread/129829 . Warning that this is getting into the guts of Torque and recompiling it and all that.

#5 @Charlie,

Good topic, may I suggest that you can also use schedule function to reset $mouseDownEaten, like so:

function MyObject::onMouseDown(%this, %modifier, %worldPos)
{
// did a fellow object already use up the mouseDown?
if ($mouseDownEaten)
return;

// do some work if you are the one to get the click
echo(%this.getName() SPC "Yay! I get the mouse click!");

// now register the mouseDown as used up for your fellow objects
$mouseDownEaten = %this;

schedule(32,%this,"resetmouseDownEaten");
}

function resetmouseDownEaten()
{
if ($mouseDownEaten) {
echo($mouseEaten.getName() SPC "ate the mouse down. I'll reset it for the next click.");
$mouseDownEaten = "";
}
}

#6 Dredging up this old thread, but I actually ran into issues with this implementation and maybe this will help someone else :). When loading a game, my main menu overlay would pop up over other buttons. Even though it was supposed to be ignoring the clicks on lower buttons the game would actually crash.

The issue seemed to be that the load game code would try to clear the screen and restart the loaded game - however, the engine was still trying to process the onMouseDown part for the other object - even though that code should have just found $mouseDownEaten and aborted. I actually had to make a short bit of code to turn off UseMouseEvents for all other screen items when opening the main menu to avoid this issue.

#7 Hmm. If I follow, you may want to change your loadLevel function to run on a schedule. Something like schedule(1, loadLevel, "levelName")

I've had a problem with loadLevel if you don't finish the current function before it runs!

#8 Not exactly, but it's in the same vein. I ran into that issue when I started my project and ended up ditching the whole loadLevel function (after the initial one). My LoadGame function just deletes the current screen objects, then reloads data and creates objects based on the save game information. What I was running into was, after it did the delete portion, it was apparently trying to run the onMouseDown code for a no-longer existing object and the game would crash out. It took me forever to realize it was because I was only handling button layers using the $mouseDownEaten scheme, and that I had to actually turn off UseMouseEvents for the objects to avoid this problem.