Prevent a click from going through GUI buttons.

[anon23814272]

There are a couple questions about this, but all of them are old. The solutions seem super poor and hackish. Is there a good way of stopping a click event when it is used on a button these days?

Edit for clarity:

My specific problem is I let you select a virtual grid space in my game. It checks for mouse clicks in Update() and then raytraces from the camera. I have buttons on the screen which when clicked, also select the grid space that is behind them from my unrelated grid selection code.

I was hoping for an easier way to prevent the clicks on the button from registering in the Update().

From the responses there are apparently no non-hackish ways to accomplish this. My specific hack is I check if the cursor is in the rect defined by my buttons and don't run my code in Update if it is.

Does anyone here know if EZGUI solves this issue elegantly?

[Extrakun]

You may have to implement a Finite State Machine for GUI and normal game components, and perhaps a master game state. When the game state detects that the mouse is over a GUI component, it will tells all game objects to go into a disabled state which would not react to any mouse click and when the mouse leave the GUI element, you will send a message to the master game state to inform that game objects can be enabled.

To detect mouse entering and leaving a GUI element, you'll have to declare a rectangle for it.

Probably not the best method for a small application with a few GUI elements. It would be helpful for a complex application with many GUI elements though.

[aliakbo]

There is a much simpler solution here which suggests

if (Input.GetMouseButtonDown(2) && GUIUtility.hotControl == 0) 
{
    //will only click if not on GUI
}

[DaveA]

Yeah we did something like what Extrakun says. Made a singleton class that holds a variable that says 'GUI is up' and a LateUpdate that clears it. Then anything that puts up a GUI thing sets that variable (GUI is up) if the mouse is in bounds of the GUI element(s) and any scripts that would need to be 'blocked' check this variable (MouseLook, FPSWalker, etc). It's not pretty, but it's really just a couple of extra lines of code in each such script, not too bad.

[system]

did what was outlined above and it’s working well, so I though I would post some code. Make a script called GUIBlocker and add this

static var isBlocking:boolean=false;

function LateUpdate () {

isBlocking=false;

}

drag it on to an empty game object

then in your OnGUI functions of other scripts that open up GUI boxes that shouldn’t be clicked “through”, add this

ix = Input.mousePosition.x;

iy = Input.mousePosition.y;

var transMouse = GUI.matrix.inverse.MultiplyPoint3x4(Vector3(ix, Screen.height - iy, 1));

var panelRect:Rect=new Rect (x,y,w,h);

GUI.Label (panelRect,someTexture);

if(panelRect.Contains(Vector2(transMouse.x,transMouse.y))){

GUIBlocker.isBlocking=true;

}

then on your objects that handle mouse clicks but where you want to ignore clicks through gui boxes, say

if(!GUIBlocker.isBlocking){

//do stuff

}

Hope that helps

[zombie_psy]

Parent a Plane to the camera, with the plane about 0.1 in front of the camera, then scale the plane so it fits behind the button that you don’t want anything clickable from behind. Optionally, unclick the plane’s Mesh Renderer to hide the plane, but retain the Collider…

Honestly, Unity should have a simple toggle box on all GUITextures to make it Transparent (overlappable clicks) or Opaque.

[BenFranklinstein]

This one works with the new GUI elements, buttons, labels, etc.
Just check _isMouseBlocked() before performing your selection action and return from the method before performing your action.

using UnityEngine.EventSystems

public void RaytraceHitMe(GameObject obj)
{
    if (_isMouseBlocked() ) { return; }
    var sb = GetComponent<MySelectionBehaviour>();
    sb.selectObject(obj);
}

private bool _isMouseBlocked()
{
    return (EventSystem.current.IsPointerOverGameObject());
}

The key method is in IsPointerOverGameObject

[Statement]

I hate to hand it to you, but the GUI is very hackish to start with so any workarounds probably are equally hackish.

I guess you are having some problem with things related such as drop down menues where buttons overlap other buttons. Right? And when you press one of the buttons in the drop down, it actually press some button that is under the drop down? It was quite some time since I did that kind of gui. The best advice I can give you is to design/work within the limitations of the gui and try to not break a leg.

Some heavy guesswork trying to remember how I solved this in the past:

Otherwise I think it is possible to do this if you make use of gui windows, and possibly they're required to be in separate game objects. It was something silly like that. I think it's a fault from immediate mode where objects are evaluated in the order they are declared in code. A button drawn under is called first, right?

GUI.Button("Under");
GUI.Button("Over");

So, the code seems to execute the Under rather than the Over button on a click. First come, first served.