Official UIElements for Runtime and the UI Builder Unite Copenhagen 2019 Talk

Have seen that package manager have new feature, we could specify path into git repo for package now. Playing with it is funnily success

"com.unity.ui.runtime": "https://github.com/Unity-Technologies/UIElementsUniteCPH2019RuntimeDemo.git?path=/Assets/UIERuntime/",

 

I can't see any support for world space positioning in the runtime examples. What's the plan for this? (specifically for VR in my case)

 

Would the screenspace solution near end of 2020 support 3d models in the UI (e.g. for showing stuff in inventory)? Right now we're using a canvas linked to a camera.

 

What is the state of Runtime support for Unity 2020.a1?

 

What is the state with current 2020.1a

 

@Digika well like the version number implies it's still in alpha. Previous tech releases were timed similarly or almost on the same day as several package releases. So my expectation would be that by the time 2020.1.0 releases, we'd see the UI elements pacakge with runtime support. So a couple of months.

 

Am I missing something or keyboard events are not implemented in this runtime demo???

 

Thx for the answer.

Well, I can't make them work. Mouse events work just fine but keydown/up events are not being fired.

This is a fragment of the code I'm messing with:

Code (CSharp):

1. Button b = c.Q<Button>("skill-button");
2.         b.RegisterCallback(delegate(MouseEnterEvent ev, Label label) { label.style.display = DisplayStyle.Flex; }, l);
3.         b.RegisterCallback(delegate(MouseLeaveEvent ev, Label label) { label.style.display = DisplayStyle.None; }, l);
4.  
5.         b.RegisterCallback(delegate(KeyDownEvent ev, Label label) {
6.             Debug.Log("KeyDown!");
7.             if (ev.keyCode == KeyCode.Keypad1) label.style.display = DisplayStyle.Flex;
8.         }, l, TrickleDown.TrickleDown);
9.         b.RegisterCallback(delegate(KeyUpEvent ev, Label label) {
10.             Debug.Log("KeyUp!");
11.             if (ev.keyCode == KeyCode.Keypad1) label.style.display = DisplayStyle.None;
12.         }, l);
13.  
14.  

 

Okay, what about 2020.1.0b5? Do we have Runtime and Editor support there now?

 

They said that the package will be released alongside the final version of 2020.1. We're still a couple weeks from that.
I'm also dying to try it.

P.S: @uDamian Do you need/want bug reports about runtime at this time? I have found a pair of them and can send them if they're of any use.

 

Then how do you plan to report runtime bugs if it does not exist yet? I'm asking if there is the rewritten runtime support in the 2020.1 beta

 

Version 0.0.4 of the runtime package has been out for several weeks now, is just not officially announced and hidden from the package manager UI. But you can use it today if you add it manually to the manifest.

 

What's the URL to add?

 

"com.unity.ui.runtime" : "0.0.4-preview"

 

Is it worth to even bother with it if they said they rewritten the structure and changed the approach? Learning 0.4.0 seems like waste of time, no?

 

Well some things pertaining runtime may have changed but the core of UI toolkit is pretty much set in stone by now. I wouldn't say it's waste of time. Most of what you write for UI Toolkit (all of uxml and uss, and most of the logic) works both in editor and in runtime. At most, you will need to change the way panels are created or updated, but i expect it to be a minor change overall.

 

Yeah it's mainly runtime performance, feature parity with UGUI, support for SRP and eventually (really far down the road) DOTS that's on the roadmap for runtime ui. But the code you write now should largely be unchanged in a years time.

 

I see.
How would I use:

for runtime?

 

You have to manually add

"com.unity.ui.runtime": "0.0.4-preview"

to the end of the manifest.json located in the Packages folder of your project. Then open unity and wait while it installs.

Once installed, add the PanelRenderer component to some gameObject, and give it your uxml and uss to render. To access the panel hierarchy, reference the panel in you script and use the visualTree property.

 

Thanks. Is there any quick... not tutorials, but rather short guide-examples for the runtime preview?

 

Yes, if you go to the package manager entry there's 3 sample projects you can import

Spoiler: Screenshot

 

Thanks, looks like they are a bit outdated for the 2020b1 tho

Code (CSharp):

1. 'PanelRenderer' does not contain a definition for 'Start'

 

I couldn't tell you, I haven't used them myself. Sorry

 

Any idea how would I tie the UI elements to the script logic in the latest preview?

 

What about support iOS in latest preview?
I built app and PanelRenderer does not show anything. May be is it ok? But I didn't find some information about support platforms

 

How do we get this? I wanted to fiddle with this (as I'm struggling with UI and think this will make it easier) but the package is not to be found in the manager...

 

Preview package. Only shows up when you tick that you want to see the preview packages. The place of the check for the preview packages depends on which version of Unity you use. They recently moved this from the package manager to the settings.

 

UI Builder? I was looking for UI Elements...

Also, found somewhere that it was only for editor extensions?

I'm really quite loss at the information thrown around...

 

You didn't really specify. I assumed your "struggle with the UI" refers to the UI Elements. My mistake.
UIElements is a built-in package.


AFAIK it is production ready for the editor UI and preview for game UI. Meaning you can start to play around with it and with the UI Builder, but it is not 100% yet in game.

 

You mean I can fiddle it but games won't work or just that some features are not supported yet?

Thanks for the info.

 

UI Builder is what you’d want to build UI for games

 

This is so absurdly dumb.

The rename wasn't necessary at all, but by god having the two names around is just going to cause so much confusion. At least consider fixing it? You have an API auto-updater, and this is a pretty trivial auto-update as they go.

 

I think it possible that there was backward incompability between these 2. It would be easy to just copy whole thing and change name, then change everything it should be changed freely, so it could mutate separately, fixing a bug and update version for the old one before deprecate, and reduce the chance to break people using current UIElements in UnityEngine namespace

If so then it obvious that rename it into new namespace is easier

Also it make namespace suggestion autocomplete become less verbose

 

One thing I would like to request, I wish you would expose everything that underline UXML to be used without any internal class, so we could create and inject our own custom system to generate UIElements token in the equivalence manner as UXML

 

I can t find that package in 2020.1.b in the package manager. How did you manage to get it?

 

Did you manually add

"com.unity.ui.runtime": "0.0.4-preview"

to the end of your manifest.json ?

 

No I did not. That helps. Thank you

 

Can someone comment on what is the current status of UI Toolkit ? @uDamian

• is it available as a package ?
• is it available for runtime ?
• Is the UI Builder released ?

 

Yes, it's available as a package. To use it at runtime, include this package reference to your manifest.json:

"com.unity.ui.runtime": "0.0.4-preview"

The UI Builder is in preview. You can add it via the package manager window after turning on experimental packages for your project.

 

Thanks. why isn't it available in the UI ? (i mean why do i need to manually update it) ?
Also - when should it leave the "preview" state? does anyone know ?

 

It hasn't even entered the preview state. That's why it's not publicly listed in the package manager. The first official preview is expected to arrive around the time 2020.1 releases (a few weeks from now hopefully). The package is expected to come out of preview around the time 2020 LTS releases (Roughly a year from now)

 

Roadmap here.

 

The runtime package broke in 2020.2.0 Alpha 15, hopefully an actual release is coming soon

 

Some info