This issue has been closed as 'Won't Fix' due to an extended period of time without updates. If this issue is important to you please let us know by posting on the AnswerHub or UDN, and Epic will re-open the ticket for further review.
User created widgets from widgets that are normally not focusable appear to break navigation when added to another widget even when focusable set to true
Example: A widget with only a text block in it (text is NOT able to be set to "is focusable" true) that has been added to another widget via the user created section can be set "is focusable" true but does not cooperate with the default navigation.
Note: This appears to work in 4.13.2
Expected: The focus would shift down/up when the down/up is pressed on the keyboard and/or controller
Result: The widget cannot be focused by default navigation even though they have been set to focusable
I am not able to find world outliner how to enable it?
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
How does TextureRenderTarget2D get TArray<uint8> type data?
How to achieve HLSL Multiple Render Target in Material blueprints?
How can i modify the param name in EQS node
Why does the REMOVE method of map container remove elements have memory leaks?
What method is used to fill polygonal regions when drawing spline mesh at run time?
Delay nodes occasionally don't fire the "Completed" output in a nativized build
Head over to the existing Questions & Answers thread and let us know what's up.
5 |
Component | UE - Editor - UI Systems |
---|---|
Affects Versions | 4.14 |
Created | Oct 28, 2016 |
---|---|
Resolved | Mar 26, 2018 |
Updated | Mar 26, 2018 |