Hey there. The default toolkit inspector works great and I really like it. It seems like telling the inspector to use the default toolkit is not persistent and I have to do it every project reload and sometimes multiple times in a single session if things got a little crashy from my dev work.
I’ve checked the project and preference settings as well as around online - is there somewhere I can read about this feature and it’s plans for the future? Will it one day be remembered that I want to use only the toolkit inspector and not revert back all the time? What if I want to release an asset that is heavily based in toolkit. Do I need to write imgui companions for all my property drawers for all time or is there an estimation where I can start ignoring imgui?
I find your suggestion interesting but, unfortunately, anything accessible via that mode is currently not officially supported and that is why there is no option in the preferences or project settings.
We certainly want to properly support that in the future, but we have work to do as enabling such option right now may cause regressions for some users.
For the time being, maybe you could look into this post to override the default inspector. I wouldn’t recommend shipping that as part of a package as it may break some projects, but it’s fine on your own and would remove the need for toggling the option.
I don’t really understand this answer since the cs source shows the default inspector is already built and unity is already giving me the option to right click and access it and just a simple prefs lookup in the default inspector to auto enable it so I don’t have to right click would do the trick.
But I will trust that there are complications and reasons to back up your answer that I don’t know. Thank you for the reply and i’m looking forward to ui elements progression.
You have the “developer mode” option enabled in preference → developer mode. If you disable the developer mode, the option to “use Ui Toollkit default inspector” will not be visible. This mode is useful for debugging, but we don’t support some features in there.
Thanks for the feedback. The biggest roadblock with enabling the UI Toolkit (UITK) inspector is performance for large inspectors. UITK has to create all the elements at once before it can efficiently display them. This initial creation can be too long for large inspectors. We’re working on improving this performance and should hopefully transition to UITK inspectors (by default) in the 2021 timeframe. In the meantime, you can force use of UITK for your own types by implementing them in UITK. This will work just fine inside the current (IMGUI) inspector. The only problem is if you want to have independent PropertyDrawers for use by your users in their inspectors. That part is still something that won’t always work and you probably need to implement both IMGUI and UITK.