Experimentors Drop for New UI System?

Understanding you are all busy -
It seems that a runtime for the new UI System is getting close to a preview. Any chance of seeing an experimental drop of the Input System that works (at least at a basic level) with that at the same time?

 

You can add the following preview package to get the UIElements runtime preview: https://docs.unity3d.com/Packages/com.unity.ui.runtime@0.0/manual/index.html

 

@recursive Thanks! I was still using the code from the demo.

I'm not finding a link for the package. Tried by manifest - guessing at the name since there is already a uielements 1.0.0 in my project (the editor?)

"com.unity.modules.uielementsruntime": "0.0.4-preview" but that didn't work.

 

That would be

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

, but it doesn't help with the new InputSystem. They simply don't work together because UIElements event system reads from Input directly. I managed to create my own event system and it more or less works, but there are missing things – e.g. can't translate coordinates properly because ScreenToPanel is internal in PanelRenderer, and even copying the code is not possible, because scale is not accessible either… Also, keyboard (in text inputs) doesn't work at all, it is too tied up with internal IME stuff in Input.

 

@ilyaryzhenkov Thanks, that did it. I'm doing something similar and mostly bypassing the internals. But not getting keyboard into text boxes will be a showstopper for me.

 

I assume proper integration is planned for later this year as the new Input System goes into 1.0.0 release soonish.

 

@recursive I think it's not only InputSystem that needs changes, I believe UIElements should also be updated. It needs

UIElementsInputSystemEventSystem

(oh… may be something different) to route InputSystem actions to Panels, taking into account transforms for proper raycasting, keyboard IME stuff, capturing events (so that keyboard events are routed to text input when focused instead of activating actions), etc.

Basically, both teams need to work together to make it good quality integration, and not like it seems to be now with copying BaseInput into InputWrapper, throwing some more WD40 and duct tape on it and calling it a day