When the chat area isn’t visible, it still blocks mouse inputs behind it. This is very annoying. I have to move my camera so that what I was trying to click on/hover over/etc is no longer underneath the invisible chat area.
8 Likes
That’s interesting, I’ll check it out.
Do you know if it’s just when the background fades? Or if it’s also when the chat window is actually closed by clicking the topbar icon?
when the chat bar is closed it doesn’t effect mouse input.
This probably isn’t the issue it seems like then. The chat window needs to be active while faded because clicking it unfades it.
Well clicking the faded chat box does not unfade it.
The video doesn’t show my mouse clicks sadly, but I am clicking when circling a part of the screen.
It would be nice if the Chat box was just not active, even when visible, as clicking it serves no purpose. The only purpose it has currently is when you are in whisper or team chat and you click the chat box (only when it is visible) it goes to public chat, which you can already do by hitting backspace twice while in the chat box.
Active is not required to sink input in GUIs: buttons will get MouseInput regardless of their Active property. Near as I can tell, Active is only necessary for blocking the Mouse from setting its Target property.
I tested what happens if I have overlapping TextButtons, and higher ones steal input from lower ones regardless of Active.
I’m not sure how this is relevant. If you didn’t block input to obscured elements, you would get two things responding to a click, which isn’t ideal. Core UI takes priority.
I thought you were talking about the Active property.
Not sure anymore, honestly. My point was that the chat window eats input because it responds to it, which makes sense to me. Active is a way to do this, but if it’s a button, then the point still stands.
If buttons can’t be deactivated by setting Active=false, then that might be a separate issue.
Can this be fixed? Sometimes in a Test Server there’s no button to make chat disappear, which forces you to disable the Chat Gui if you wanna test any UI that goes in the top left corner.
Oh, so the problem is that it still grabs input after clicking the topbar button? Why didn’t you say so? 
The problem is, when clicking the faded chat box, it steals input and does nothing with it. It has been recommended that the chat box not steal input if it is not visible and/or faded.
1 Like
Please fix.
Gonna bump this again
This should be coming fairly soon. I coupled it in with some other chat edits and it’s all merged into the CoreScript GitHub repo.
4 Likes
Bump; this is still a problem
1 Like
Bump, chat was changed but still no fix for this. I think chat box might’ve even gotten bigger
1 Like