Setting UMG navigation rules at runtime
I have a very simple menu to browse through a gallery of images, containing buttons for "Previous Image", "Next Image" and "Back out of this Menu". In the graph for this menu widget, I disable the Prev and Next buttons when the ends of the gallery are reached.
Disabled buttons still accept keyboard focus, which is not ideal for the user in this case, so I've tried to work around this by changing the navigation rules whenever a button is enabled or disabled, using "Set Navigation Rule".
However, it seems that none of the changes I make using this function actually work. I can see that the navigation rules point to the correct widgets if I print them out using Get Navigation, but the actual behaviour when I attempt to navigate using the keyboard is always unchanged from the initial rules set when the widget was first created. Is there an obvious reason why this isn't working?
Alternatively, is there a way to disable and enable "Is focusable" for buttons at runtime?
asked Sep 11 '17 at 04:50 PM in Blueprint Scripting
Follow this question
Once you sign in you will be able to subscribe for any updates here