Developer Notes

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.

Description

The release execution for the tab key fires even though the tab key is still held down. This makes it so that the Release will sometimes fire twice (once while held down and another when the key is released). This happens if a focusable widget is added to the screen and the input mode is set to focus on UI.

Steps to Reproduce
  1. Open the editor
  2. Create a new widget blueprint
  3. Add a button to the designer tab
  4. Save and compile
  5. Open the level blueprint
  6. Create the blueprint in the attached image
  7. Play in editor
  8. Press and hold the tab key
  9. Notice that both print strings fire off even though the Tab key has not been released

Expected: The release execution would not fire off unless the key has been released
Result: The release execution for the tab key fires even though the tab key is still held down. This makes it so that the Release will sometimes fire twice (once while held down and another when the key is released)

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

2
Login to Vote

Won't Fix
ComponentUE - Editor - UI Systems
Affects Versions4.12.5
CreatedJul 12, 2016
ResolvedFeb 10, 2017
UpdatedApr 27, 2018