Why does clicking on my GUI activate the GUI underneath it?

[codepoet]

It is a simple question really, but it is baffling me, and I am reluctant to do more development on any of the mods I have got queuing up waiting for some attention until I have an answer to this, because I can see it ruining things over and over again. What is the solution? Why to I have this click through behavior? I have seen it on other mods too, and then not on others, but I can not get to the bottom of what the differences are? Can someone just tell me - what am I doing wrong.

[Faark]

Still no one? Afaik / To my little knowledge: There are a bunch of different system like EZ GUI (seems to be used for KSP's interface), UnityGUI (or however Unitys easy built-in UI system is called; used by most mods) or KSPs other input handling and it would be surprising if they would work together nicely by default. I once came across UIManager.instance.DidPointerHitUI, what kinda does the opposite, but neither tried it nor can i remember where. And this ofc wouldn't work with UnityUI. Maybe using EZGUI in mods would be the best approach. Anyone done this? Any examples for using this from script only?

What mods for example are you talking about? Figuring out what they do differently should be doable.

[blizzy78]

You can use the InputLockManager to prevent click-throughs. Basically you would be locking KSP's UI as long as the cursor is over one of your windows.

[blizzy78]

Oh, and there's EditorLogic.fetch.Lock(), too. I wrote a class that deals with that in the VAB/SPH.

[codepoet]

Thanks, that is just the sort of answer I was hoping for. I will look into it.