Controller support

[jacobc16]

I can't find any info on controller support or using the keyboard to navigate the UI. Is this something we have to write ourselves or did I overlook it?

[dkonik]

Nova does not currently provide d-pad/keyboard navigation out of the box, though we expected this would be a requested feature and will definitely add support for it if there is enough interest! If you would like to see this added to Nova, I can change this from a question to a feature request.

[jacobc16]

Ya, that would be great!

[xin0898]

Would be the last piece of the building block to make this tool brilliant!
Making game with potentially porting to consoles, switches in mind here, if knowing that NOVA UI can support different kind of input regimes out of the box would make me a very happy person on earth

[GamePowerDev]

Yes x1000, controller support is a must these days now that handheld game devices are becoming way more popular, console games require them and overall games that only support mouse and keyboard are a dying breed.

[adgray1]

Version 1.1.0 has been released with our new Navigation API to add Gamepad/WASD support to your Nova-built content!

The documentation has some complete examples for how to add simple keyboard navigation to your own input manager, and the InputManager script in the UIControls sample now also includes similar functionality!

[dmerner]

Hi Adam,

Is there an example on using Gamepad/WASD controls for navigation without the use of a NavigationIndicator like in the UIControls example? I'd prefer to just have buttons.etc highlight as the user navigates across them (without the use of a mouse).

I haven't been able to get the Gamepad/WASD controls to actually work with OnHover in the gesture system. Is there a way to have a UIBlock work with OnHover when it's focused via Navigation.Focus/Move? Or does OnHover only work for mouse input?

My current method is to just use Navigation.OnNavigationFocusChanged to manually set the background colors, but using the gesture system would probably be a bit cleaner.

[adgray1]

Hover/Unhover only fire when calling into Interaction.Point. The closest alternative to those events in the context of navigation is Navigate.OnMoveTo ("hover") and Navigate.OnMoveFrom ("unhover"). So you have a couple of options:

1. You could either change any Gesture.OnHover/Gesture.OnUnhover event handlers to handle the Navigate events instead
2. In your Navigation.OnNavigationFocusChanged callback you could create a new Gesture.OnHover struct, and call focusedUIBlock.FireGestureEvent(myHoverEvent) (doc) yourself - and also unhover the previously focused UIBlock in the same way with a new Gesture.OnUnhover struct (e.g. previouslyFocusedUIBlock.FireGestureEvent(myUnhoverEvent)).

That second option is potentially a bit simpler and basically the same as what you're currently doing, but it will allow you to remove any duplicated visual-state-setting code :)

Hopefully that helps, but let me know if you get stuck or need me to elaborate on either option!