Same answer?
Disabled elements get the .unity-disabled style which sets opacity to 0.5. You can define a style with the same name to override this, if you don’t want the overlay underneath to be semi-transparent.
I do this in the core style sheet used by my primary theme style sheet, so this behaviour automatically affects every UI overlay in the game.
EDIT: To be clear by disabled I don’t mean I hide them, I call VisualElement.SetEnabled(false); so they stop receiving events and such.
Ah, I thought by disabling you meant changing display or visibility of element. I understand now, thanks
a couple of users here are hardcore prounity and they will never accept anything wrong with the engine or the company. Not even one single thing. They are free to do this but just so you know and not start doubting what your experience is with the engine.
From my experience NOTHING in the engine ever worked 100% as it should or how a sane person would had expected it to work. There were always some fundamental obvious functionality missing, attempts to get the unity devs recognize that the function is required were most of the time futile.
Just so you don’t get crazy, just focus on the things you have that work, make them work and move on to the next project.
Well know Fan-base. 
Sure they are. Infact I was doubting with the whole UI System itself to bring some clarity for future users that would want to start using it. I just declared my own experience with it.
I have read a tons of forums (including X, Reddit, stackoverflow) regarding the whole situation about the UI in Unity and I was right many people still complaining till today that we have no UI solution at all. Just looking at Godot and Unreal they have a very solid UI system and they’re still improving it and comes with quite all neccessary functionality. I don’t really want to switch Engine because I like it but at the same time I can’t use it cause lack of very critical features for literally a decade. I know that Unity is more into AI stuff tools but who ever gonna use them? lol
After reading bunch of forums I do realized that there’s nothing that we can do in order to change things in this engine because all decision comes directly from Unity.
Many people was asking for only one features that never comes in years and Unity stop answering to that forums. Even here they stop answering to their needs. Many of them get a conclusion that UITK is already deprecated. For example on the latest version of unity 6001 i think it is an alpha. There’s absolute no trace of UI. But they’re still fixing bugs on old uGUI. lol
Well because techincally all the plugins and extension comes from other’s people that they bought and this is why they have such a difficult time to maintain those plugins & frameworks
performace should not even be a discussion point. it pales in importance compared to the main thing (which you also briefly cover, but not enough):
you should be more worried that they don’t seem to support UGUI with the same speed as UI Toolkit, which makes it seem that UGUI will have IMGUI’s fate for runtime UI, but the misunderstanding here is:
because IMGUI is really hard to work with, and it made sense to replace it, UGUI should follow the same path – but I can literally do anything with it, visually, I can leverage the mature 2-decades-old concept of Game Objects (Unity founded in '04), the already-mature prefab system and the sweet prefab nesting (those who were here before prefab nesting know very well what a pain it was to create reusable components), so after they’ve achieved almost perfection in their UI system, they now say
Note : Unity recommends you to use UI Toolkit for your new UI development projects. However, Unity UI (uGUI) and IMGUI are appropriate for certain use cases, and are required to support deprecated projects. For more information, see the Comparison of UI systems in Unity.
which is sending some poor beings (new devs) on a doomed path filled with rabbit holes where a decade-old complete solution is already fully capable
they push this UITK as what appears the successor of UGUI, which is not. I do like having the ability to allow more designer-minded folks contribute easier, stylesheets, better git diffs and all, but UITK is dead on arrival IMO (at least for runtime – I’m not talking about editor UI), because it completely disregards the “shoulders of giants” UGUI is standing on.
if it’ll ever become the 1st real option used by real devs (read people earning from their projects or working at companies that need to move fast), it’ll be because of enormous efforts on Unity’s part to force something to be true (persistence eventually wins), with resources that should’ve been used in more pressing areas
what should happen instead: they should be 2 parallel way of doing things, with interop (UITK element that can display any UGUI element and vice-versa)
it’s incredibly interesting how many people agree with the official stance, and how few people agree with OP. for me, it’s just a no-brainer, and I know ugui inside-out since day #1 like 10y ago
I’m also deeply involved in ai python dev and llamaindex/langchain are the most popular frameworks in the space – there is nothing, nothing that compares to first-hand experience, i.e. you going and trying to use those frameworks in a real world, serious, project that’s actually intended to make money, you know, the stuff needed for lambos. only when you’ve come pretty far into the project you realize you’ve actually been rewriting most of their functionalities (somewhat similar to a refused bequest code smell), and that you’d actually be better with just using a lower-level approach (i.e. using the underlying libraries they use) to achieve anything you want. I wrote a long github issue just a few days ago about this and how many hours I’ve spend due to unintuitive design decisions in the llamaindex framework (it still does ok for RAG, but not for pure LLM needs – calling native apis is way better)
ugui minus imgui
does not equal
uitk minus ugui
First of all I need to be thankful for understanding the real origin of this thread. A fresh breath of air!
And this is why appearence of UITK should make more sense in terms of that but it should stay that way.
Because primarly it was made for Unity Editor and that awesome because you can adjust or add things visually without even need to code but no more than that.
If they kept improving uGUI I already can start to see a visual futuristic improvement on that.
It could be much more.
I strongly believe they should focus into more a “GAME” UI System. I still can’t get it why they decided to go into more Web Engine. It makes me insecure if that was for the first april fools day release as a joke that turns into an idea for the devs.
Well in theory everything that we get inside UI TK is experimental none of those thing is done well. Even the rotation is absolutely broken. I’m not expecting that they will ever bring other features from the roadmap since they couldn’t even get a working rotation. lol
By the way to make it more funnier here is the magical futuristic code of UI TK:
Tween.Custom(0, 360, duration: 5.5f, onValueChange: newVal => templateGemContainer.Q<VisualElement>("ShinnyCircle").style.rotate = new StyleRotate(new Rotate(newVal)), Ease.Linear, -1);
and yes so called “Transition animations” injected into UI TK is pure trash if not worst. You can do much more cool stuff using any Tween you want. Since you are not limited of using it.
For me looking at those simple issues that it has it’s already dead. I’m not even speaking of all features that is missing in UI TK but the things that’s already there. Absolutely unstable it already throws million of issues when you try to diving deep into it. I’m not surprised if you can finish a flappy bird using UI TK and barely a doodle jump.
Exactly since old uGUI is deprecated they should start to learn UI TK which many of them will do and that a big K.O.
I’m already thinking that UI TK won’t be the successor of uGUI since only 10 % is using it and other 90% seeing it from all over forums still not agree with that which will lead Unity to take a completely different approach. From what I start to see is that they stopped already bring any news to it since they realized already there’s something wrong with that path. There’s so many complains than the actual compliments of using it and it couldn’t be a successor nor a replacement for the current uGUI it’s just a NO for many many people. Even experienced devs is not happy about that. I still seeing people make the whole courses on old uGUI and it still used today. We are in near 2025 and people keep making courses for it.
Even if you start search for tutorials or documentation it simply doesn’t exist. If you see some of the tutorials it’s more like explaining basics stuff but not really anything new. People just can’t show anything new from it because it’s not capable of it. UI TK is not more than just basics stuff that an old uGUI can do that better like 10 times and even tho you can extend it simply without USS, UXMLS etc…
Why just not taking some time to make uGUI even better.
Why then they didn’t rewrite from scratch Json Utility? Camera? Text component? You may ask why? The reason behind it is that even if they start rewriting it they can’t finish it. Like the same thing with the current UI TK they just left it.
Even for a simple thing in UITK you need to write your own rules when you can do that simply on uGUI without recreating a wheel.
As I said previously uGUI is well made but it need adjustments and that’s explainable because it wasn’t updated for decades. But it would take less time doing it than recreating a whole new UI System which barely no one’s is gonna use it.
It’s not more SHOULD it’s a MUST of having 2 parallel way.
That’s the most shocking part as well. Which makes no logical sense to me. It’s incredibly strange how some people likes unfinished work completely unstable and still keep going into a defense on saying everything is fine and it should comes with time. Like what they’re trying to stand off? Unity doesn’t even care about them. They even stopped to answering on many complains and issue that UI TK brings because they’re too many.
Yeah it’s more home sweet home already.