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.


A user found that when renaming a binding for a mouse down event for a border widget that the event would no longer fire off. They only worked as long as the default name was used.

Steps to Reproduce
  1. Open a new project
  2. Create a new widget blueprint
  3. Open the widget blueprint
  4. Add a border to the designer tab
  5. Scroll to the bottom of the details panel for the border
  6. Create a new binding for mouse down
  7. Place a print string in the function
  8. Compile and save
  9. Open the level blueprint
  10. Add the widget to the viewport and show mouse (image for reference)
  11. Click PIE
  12. Click border a few times
  13. Notice that the print string fires off (expected)
  14. Stop PIE
  15. Open the Widget blueprint again
  16. Change the name of the mouse down function to "MDFun"
  17. Compile and save
  18. Click PIE
  19. Click the border a few times
  20. Notice that the print string no longer fires off

Expected: Print string should fire when clicking the border on screen
Result: the Print string does not fire after changing the name of the mouse down function

Have Comments or More Details?

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

Login to Vote

Won't Fix
ComponentUE - Editor - UI Systems
Affects Versions4.
CreatedJun 26, 2015
ResolvedDec 14, 2018
UpdatedJul 14, 2021