Two simple GUI noob questions

[monkeybrother]

Hi. On mouse over I spawn a script that shows a tool tip (among other things). On mouse exit, the script is destroyed. This is necessary, since I have a lot of objects and add more constantly. How can I set the GUISkin in the code? Where in the project structure should I put the actual GUI file?

Second question: How can I make the GUI invisible to the mouse? Whenever the GUI is over a “tooltip object”, the tool tips stop working.

Thanks!

[anon_43237147]

@monkeybrother

Hi. On mouse over I spawn a script that shows a tool tip (among other things). On mouse exit, the script is destroyed. This is necessary, since I have a lot of objects and add more constantly. How can I set the GUISkin in the code? Where in the project structure should I put the actual GUI file?{/QUOTE]

I’m not sure what you mean by ‘spawn a script’, or why that would be necessary, but setting the GUI skin is as easy as “GUI.skin = skin;”. You can put the GUISkin asset anywhere in your project structure you like, it doesn’t matter. However, getting a reference to it might be a little trickier if ‘spawn’ in this case means ‘create an instance of’; either the ‘spawned’ script will need to load the skin via LoadResoure() or similar, or the script that ‘spawns’ the other script will need to have a GUISkin reference to pass in.

@monkeybrother

Second question: How can I make the GUI invisible to the mouse? Whenever the GUI is over a “tooltip object”, the tool tips stop working.

Again, not quite sure what you mean; if the GUI was invisible to the mouse, it wouldn’t be possible to interact with it. I take it the ‘tooltips’ you’re talking about aren’t related to Unity GUI’s tooltip support, but rather are GUIText or similar game objects that exist in the 3D world? Are you saying that if a Unity GUI control (as created by the GUI.* / GUILayout.* functions) is under the mouse, you aren’t getting OnMouseOver() events in scripts attached to game objects in your scene?

Usually people’s complaint is that interacting with GUI elements does fire mouse events on MonoBehaviours, leading to confusion when a GUI interaction triggers in-world side effects. It sounds like you’re seeing the opposite effect?