Any manipulation of a string results in the allocation of a full new string. Most packages are immutable, including packages downloaded from the package registry or by Git URL. In C#, all strings are immutable You cannot change the contents of an immutable (read-only) package. I honestly can't call it other than a mess.Handling strings and text is a common source of performance problems in Unity projects. So here is a quick look into what a new user experiences when he tries to use a new flashy Unity feature. And I still don't know if what I did is right or if due to packages version missmatch I just broke something. This is not a good example of how one makes features. So many questions and most importantly I just wasted an hour just to try to figure this whole mess out. So right now I'm in position where I have no idea how many packages they made, which one is supported by one another, which one is installed by default and why builder is not installed by default too, why builder is not compatible with currently installed UI Toolkit by default (which btw, I believe, is called Unity UI now but is not updated anywhere in documentation). To enable runtime support, install the UI Toolkit package." and gives a link to the large multipage forum post which I really don't care to read to be honest and it probably should be a part of documentation if it contains any important piece of information. However, right at the top it says "Your project is not configured to support UI Toolkit runtime UI. After I installed the package, I finally was able to access the UI of the "UI Builder" via Window > UI Toolkit > UI Builder. I cleared it so unfortunately I can't show it, and it is not coming back after I reinstalled UI Builder, so I guess I should be happy then. So okay, after all this mess of a user experience I finally installed UI Builder and boom! It gave me a compilation error in the console. After additional research it turned out UI Builder is an experimental package which is not installed by default and you have to enable experimental packages just to see it in the list (I'll skip the details how complex and counterintuitive that package manager setting window looks). " Great!" I thought again as I have Unity 2022, so it should be also part of it, right? Right? Additionally the very next line says "Under the Editor window, select Window > UI Toolkit > UI Builder". So I started reading and my eyes fell on the line almost at the start of the page "As of 2021.1, UI Builder is now a core feature of Unity.". " Great!" I thought and went on to this next piece of invaluable information just to start tinkering with my UI. And gives the link to its documentation page. " Strange" I thought and went on to the official Unity tutorials page which tells me that for opening UI Document files I need a thing called UI Builder. However, it was not the case here since Windows OS showed me the screen "Select Program." for this type of file. All my UX experience led me to believe that I can edit it by double clicking it. So by clicking random buttons across different windows I managed to create UI Document in the project folder (that's because I just heard somewhere UI Document term, otherwise I would just die in an abundance of UI systems that exist in current Unity version alongside each other). Which is strange I thought, because "Samples" one doesn't really work and the second one is just a debugger, so where is the main working window for this new feature? First of all, the dropdown is a mess and Windows -> UI Toolkit is only showing two submenus - UI Debugger and Samples. Today I wanted to tinker with new Unity UI Toolkit, so I installed the latest Unity 2022 version and created 3D project. This is my personal little experience and rant about using UI Toolkit.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |