The following “New Item” button is covered by a black button with its transparency set to 0.8 and active set to false:
Active=false is supposed to prevent mouse events from going through – it does its job and intercepts the click on “New Item”, but doesn’t prevent the hover over highlight. If the button can’t be clicked (e.g. active=false button on top of it), it shouldn’t be highlighted on mouse over.
AutoButtonColor = false
I want the button to be highlighted on mouse over when it’s able to be clicked – I just don’t want it to be highlighted when it can’t be clicked. Highlighting it when it can’t be clicked is misleading (and probably unintentional) and should be fixed.
I know. Set both of them to false or both of them to true.
BOOM problem solved quicker than Shedletsky earns a million robawx
Yes, I’m aware I can set AutoButtonColor to false every time it gets covered, but this is not a help request – it’s a bug report. And no, neither setting both to false or both to true solve the problem. Setting both to false would mean they would never be highlighted no matter what (the intention is for them to be highlighted whenever it’s possible to click them and you mouse over them) and setting both to true results in the same problem demonstrated in the OP (both of them are set to AutoButtonColor = true)
Bro.
If you don’t want people to be able to click the button but want it to hover set Enabled to false and AutoButtonColor to true.
If you don’t want people to be able to click the button and don’t want it to hover set Enabled to false and AutoButtonColor to false.
I’m sorry if I’m missing something but it seems like this is a simple solution.
The button can be clicked normally. When this is the case and it can be clicked, it should highlight on hover.
When the button is covered up by a transparent object object, it cannot be clicked. This is intentional and the purpose of setting the active property of what’s covering to to false (setting active to false intercepts mouse events and prevents them from reaching GUI objects on lower ZIndexes)
When the button is not clickable, when it’s covered, it should not be highlighted on mouse over because it implies that it can be clicked even though it can’t because it’s covered by an active=false GUI.
I don’t know how I can word this any simpler.
Oh. Make the GUI’s transparency like 0.99.
The GUI’s transparency is already at 0.8
Also, I know how to stop the problem as I mentioned earlier – I don’t need help finding out how. This is just a bug report. That’s why it’s not in Development Discussion.
Ohhhh.
Sorry for wasting your time then.
That’s your problem, setting Active to false makes the GuiObject not interact with the mouse… Set Active to true on the cover if you don’t want any input to go through it.
It does it even with Active=true. I guess Active is just broken all around.
“This property currently does not work as expected for most GUI objects.”
I’ll experiment with it some more and then make a bug report later.
The Object Browser description is the exact opposite of that too:
“If true, this GuiObject can fire mouse events and will pass them to any GuiObjects layered underneath, while false will do neither.”
It says setting it to false will stop it from passing mouse events.
Active=true blocks 3D-space events; it does nothing in relation to other GUIs. Regardless, this is still an issue since GUI mouse events aren’t respecting z-order.