Describe the bug
I'm having a bug with the "Show Custom Context Menu (NEW)" action. I'm using it to build an emoji picker, as you can see in the attached screenshot. Unfortunately, from time to time the menu doesn't show up at all. The issue is almost like this bug report, except it's not related to fullscreen apps (I never use them). The context menu is invisible, but still clickable, meaning I can click on a emoji to insert it (even if the menu is invisible).
I never made the bug report because I didn't managed to understand what could cause it or how to reproduce it. It just happens from time to time. I thought it was related to having several monitors, but I recently faced it while not connected to my external monitors. My only guess is that it could be caused by Mission Control, when having the "distinct spaces" option enabled (see screenshot). I'm guessing this because usually when it happens, it still works fine on another space.
Let me know if I can try anything to help you narrow down the issue.
I am also experiencing an identical issue to this - I have a global keyboard shortcut that used to show a custom context menu. However, the custom context menu has recently stopped showing (v4.318)
I know that the shortcut is still triggered OK, because I ticked 'show when shortcut is triggered' under 'HUD Overlay' and the HUD label is coming up when I press the key combination.
As per previous poster, let me know if I can test potential resolutions etc.
@Andreas_Hegenberg Is there any logs I can send you to help you troubleshoot this issue? It just happened now. Triggering the action on another monitor, then back on my main one is what allowed to fix it.
Note that my issue may be different than the one described by carlosp_uk since for me it just happens from time to time, whereas in his case it seems to be consistent.
I'm experiencing the same issue. In some cases, the context menu that I mostly use does not appear. I have noticed that this usually happens when I am using full-screen applications and open the BetterTouch window. I have to restart the application every time I make a change in BetterTouch settings to get the menu display back.
Thanks for looking into this Andreas. Unfortunately for me it's totally unrelated to full screen apps, I never use them.
I'll still try this new build to check if it solves it by any chance.
I just tested the latest alpha version 4.423. The issue doesn't seem to be completely resolved.
I made a short video illustrating the issue. I noticed that when I bring up the context menu on the fullscreen application, it appears on the desktop instead of within the fullscreen application.
After several days of use, the bug continues to appear randomly, but less frequently than before.
I can't figure out the true reason for the bug and under what conditions it no longer appears correctly. On some occasions, the bug occurs when I open the BetterTouch configuration panel.
The bug consistently appears when using applications in full screen; the menu displays on the desktop instead of on the full-screen application. Only a restart of BetterTouchTool resolves it.
I thought it was fixed for me, but no it just started again now. No monitors attached. It's definitely related to Spaces.
Here's a screen record of the issue attached. As you can see, when I click on the Play icon, the menu doesn't show up. And as soon as I move the BTT view to my Space n°1, it shows up. Moving it again to Space n°2, 3 or 4 causes the issue again. It's as if the menu was somehow glued to a specific Space for some reason.
Let me know if I can help in any way by checking logs or else. At the moment I haven't restarted BTT on purpose so the bug is still occurring.
The issue still occurs, in some cases, the menu doesn't want to appear anymore. Have you been able to find a solution? Every time the problem happens, I have to restart Bettertouch.
Thank you for your feedback, the issue seems to occur when switching monitors. I use an external monitor at home with the computer in clamshell mode, and at work with the internal computer screen open and another external monitor. I have also noticed that the problem can occur when opening the BetterTouch configuration window. Hoping that this can help you.
The menu display issue persists. I've noticed that it remains stuck on the desktop in some cases and does not appear correctly in the full-screen application during usage. The only way to make the menu display properly is to restart BetterTouchTool.
I have created a short video demonstrating the problem, hoping it can assist you.
@Andreas_Hegenberg My guess is that in some conditions, the action isn't able to find out the current active space. So since it doesn't find it, it aborts without showing the menu.
I'm saying this because when it happens, if I move my cursor on another monitor, then it will show up. Also, if I switch to another Space on my main monitor, it will show up. It definitely has something to do with detecting the current Space.
Note that in my case I'm never using Fullscreen apps. But it's pretty normal that the issue also arises with Fullscreen apps since they create a new Space.
Could you maybe suggest some actions which may behave the same way to help troubleshoot? Like an action which first finds the current monitor/space?
If possible please try 4.651 alpha (uploading now)
While I wasn't able to reproduce the behavior with quitting fullscreen chrome, I found that on Sequoia beta it wouldn't show up at all on full screen spaces. I was able to resolve this by modifying the settings of the (invisible) window that is used to bring up the context menu. Maybe this will also help on macOS 13.
@AnthoPak the action indeed uses fullscreen detection, but only to change the behavior slightly. It would still show up even if it detects the incorrect state.
Instead I think it is somehow related to the window that is required for showing a context menu, but I'm not yet sure exactly.
Thank you for your responsiveness. The problem seems to be resolved with this alpha version. Based on my initial tests, when I close Chrome as well as other applications that were also causing a problem, the issue no longer appears. I will continue to monitor the behavior of the Custom Context Menu. I will be able to fully enjoy this option without worrying about it glitching.
Thanks for your answer. I've just downloaded 4.652 alpha, I'll use it for a few days and report back my results. Since on my side I've never found a reliable way to trigger the issue, it seemed random.
