When I open my Elements file directly by double clicking on the file, all opens well and the Elements Menus work from the outset.
However, if I open the program first and after the splash screen appears, I double click on my file in the splash screen, I find the Elements menus do not work at all. If I then click the desktop and go back to my Elements file, the menus then begin to work.
My computer is a 2019 MacBook Pro 16" Intel machine with Mac OS 15.5 and the latest version of Elements.
deja vue April 21st and May21st and now June20th???
danDan C.Founder, Realmac Software
Well, that is very strange…
I did a quick Google and it seems other users have this issue with other apps. I really think this is a system issue and not something we can fix.
1 Like
I did a quick Google and it seems other users have this issue with other apps. I really think this is a system issue and not an issue with Elements. Sorry we can;t be of more help on this one.
Perhaps @elementsbot can search the web for a solution.
Browse Web
Reading https://forums.realmacsoftware.com/t/menus-not-working/48197
Browse Web
Reading https://forums.realmacsoftware.com/t/menus-not-working-in-elements/47240
It sounds like the issue might be more related to the macOS system itself rather than Elements specifically, as Dan mentioned in the forum. This problem seems to have occurred with other apps before.
However, a common workaround is refreshing the app’s focus by clicking out and then back into the app, as you’ve experienced.
If the problem persists across updates, it’s always good to ensure macOS and Elements are fully updated. If the problem remains, consider reporting it with thorough details on machine and OS specifics to get closer to a resolution. If you need someone to investigate, consider reporting the bug to Apple as well.
I thought I would raise it again adding something which I hadn’t seen before, in the hope it might ring a bell with one or more of the programmers.
As for me I don’t have this problem with any of the other programs I use on the Intel machine.
Incidentally, this problem does NOT happen on my M4 Silicon machine. Both have the same Mac OS 15.5.
Cheers.