Steps to duplicate:
- Open a project in Unreal Editor on Mac. Take note of the menu bar, but don’t click on it. It has the correct entries right now.
- Open a blueprint for editing. Dock the editor as a second tab of the main window. Take note of the menu. It should have the correct menus, such as the additional “Asset” menu that appears when blueprint editors are focused.
- Click on the “File” menu twice (open it and then close it without selecting an item)
- Click back on the main tab. The menu will not update.
In short, if you open and close a menu, then switching tabs won’t update the menu. This can be worked around by clicking somewhere inside one of the editors, and then switching back and forth between tabs.
Hi ,
Thank you for submitting a bug report. I have reproduced the issue and logged it as UE-39294 which you can track on the following link: Unreal Engine Issues. Please be aware that since the issue must be reviewed and prioritized by our development staff, it may be a while before it can be addressed.
-.
Yep, I am getting used to the drill now. Just starting as many wheels turning as I can (I’ve been submitting pent-up issues lately). 
Whoah, hey, Issue UE-39294 is linked to the wrong answerhub post. It goes to something completely unrelated. Can you update that to point to this post? I mean, the text is obviously from this, but the link goes to some crash report.
Also (sorry for bugging you so much), what’s the best thing to have under “Affected” on the Issue? I have observed this from 4.6.x up through 4.14.0. I don’t know if it would be more effective for the issue to list that range (I think issues can list ranges, right?) or if it should just list 4.14.0, or what. What’s the best thing? (Or does that field pretty much get ignored so I just shouldn’t worry about it?)
This is what you should see when navigating to the provided link and searching “UE-39294:”
Let me know if that is not the case or if this is what you are seeing, if it does not describe accurately the bug you were reporting.
As for what to list for the Affected field, please list the most current version of the engine you are experiencing the issue in. If you did not experience the issue in the previous version of the Engine, make a note that the bug is a “regression.” -That will help us immensely!
, If you will click at the button immediately below the issue title:
…you will find that it takes you to a completely unrelated answerhub post, instead of this post.
For the Affected field, I have reproduced this issue in 4.6, 4.7, 4.8, 4.9, 4.10, 4.11, 4.12, 4.13, and 4.14. I have never used an earlier versions than 4.6.
This is now fixed. Thanks for pointing that out.
