Every time I try and create a floating menu that I want to stick in the top right corner of my screen (for example), the menu just flings itself off screen! And if I select the "Don't let it go off the screen" function, it just sticks itself in the bottom left corner.
For amplifying information: positional (x/y axis) offsets are 0.
What am I doing wrong?? Or is it just broken 
no, that works fine. Can you post a screenshot of your config, then I can tell what’s wrong.
Not sure this contains all the necessary info, but I tried my best.
Thank you!
This looks correct!
Could you maybe export the menu to a file? Then I could check how it behaves here. (Right-click => export to file)
Ah, the problem is caused by the z-index. You set it to show at the desktop - which is fine, however then you need to account for the menubar yourself.
Setting a -40 offset should do the trick:
Hmmm, I still can't get it to work, oh well. Thanks for the help!
Any update on Widgets coming out?
are you looking at your desktop and have set a negative y margin? (By using that z-index, you placed the menu behind everything else - even behind the menubar, thus the negative y margin is required)
I have gotten it to work in the past, perhaps I just need to reset everything.
Even when I do a "Max float on top" with putting the center of the menu in the center of the screen, it doesn't work.
Is there an article somewhere explaining how to reset all BTT settings and configurations?
Thanks!
in that case the menu is maybe hidden? you can press the toggle visibility button at the top of the config to force it visible
There should be no need to reset your settings for this
Okay I believe I found the issue... I was using a Remote Desktop connection (Jump Desktop) and through that view I was unable to properly set the menu in the correct part of the screen for some reason. When looking at the actual screen it looks fine.
Sorry for me being dumb. Thanks for your help!
Not sure if Remote Desktop issues are a known issue, but I didn't know that it was a limitation!
maybe because the reference frame is set to „built in screen“ - the remote desktop almost certainly doesn’t identify as the physical / built in screen