Best Way to Add Navigation Input
Posted: 20 Sep 2022, 20:51
Hello Noesis forums,
I'm looking into adding input so users can navigate through a Noesis interface using a gamepad or external device or whatever they choose to bind for these actions.
I've found the MoveFocusAction class which looks to be what I want, but when I put it in my xaml using the recommended syntax (XAML in https://www.noesisengine.com/docs/App.I ... ction.html) I get the error message: [NOESIS/E] MainWindow.xaml(13): 'Right' is not a valid value for property NoesisGUIExtensions.MoveFocusAction.Direction. I think the tag itself isn't being recognized and the error message is a little misleading.
I'm including <NsApp\MoveFocusAction.h> and registering it Noesis::RegisterComponent<NoesisApp::MoveFocusAction>(). Something else seems to not be right with how the NoesisGUIExtensions are getting read.
Also once I get that figured out, is there a recommended way to trigger the MoveFocusAction? I'd like to use our engine's current control binding infrastructure and call MoveFocusAction when bindings for those movements are called (up, down, left, right, select, etc.).
I'm looking into adding input so users can navigate through a Noesis interface using a gamepad or external device or whatever they choose to bind for these actions.
I've found the MoveFocusAction class which looks to be what I want, but when I put it in my xaml using the recommended syntax (XAML in https://www.noesisengine.com/docs/App.I ... ction.html) I get the error message: [NOESIS/E] MainWindow.xaml(13): 'Right' is not a valid value for property NoesisGUIExtensions.MoveFocusAction.Direction. I think the tag itself isn't being recognized and the error message is a little misleading.
I'm including <NsApp\MoveFocusAction.h> and registering it Noesis::RegisterComponent<NoesisApp::MoveFocusAction>(). Something else seems to not be right with how the NoesisGUIExtensions are getting read.
Also once I get that figured out, is there a recommended way to trigger the MoveFocusAction? I'd like to use our engine's current control binding infrastructure and call MoveFocusAction when bindings for those movements are called (up, down, left, right, select, etc.).