Floating window error since update

Bugs or Unexpected Behavior
1

Hi Andreas,

since the new update macOS Sonoma runs into problems with firing up floating window. Always I use FN+L to show up the web-preview (I think that's the used term). Yes, this was buggy as many times the window stayed just white (empty), but that could be also an error by the website blocking, cookies etc. What is new with the update, that

  1. the floating window edges are much more responsive. I set it up after your manual back in the days that when mouse cursor leaving the window, it disappears, yet I can click and drag the borders to move that window anywhere. Now the window closes much more "earlier" - or more "inside" of the window already.
  2. having that problem, I need to open again with FN+L. New error here is that macOS Sonoma in many cases suddenly fires the error-sound (system). No window is loading. If a text document is open, the cursor sets a "l", so BTT and macOS are in conflict about interpreting the key command FN after the 1st time.
    -> workaround: if Mail.app is open -> I switch to Finder. Then the FN + L is free again.

Weird behavior which is there since the update. I did not change macOS Sonoma. I use FN+L every couple of minutes while working, that's why I claim it is a "bug". :slight_smile:

Best Regards :slight_smile:
Johannes

2

Can you share that menu or is it something private?

1.) was most likely a bug before - the window was larger than actually displayed and some invisible part around this was interactive even if it shouldn't have been. There are ways to achieve that behavior if you really want it :slight_smile:

2.) Could mean that secure input mode is active on your system. Fn based shortcuts only work if that mode is not enabled. BetterTouchTool shows like this if that mode is active:

At the very top of the menu:

image
image1208×786 95.4 KB

3

Yes I will send to you today.

  1. okay then I will overwork these settings.
  2. no, secure input is not activated and not shown in my menu list.

Addendum:

  1. before the update, my text inputs in the floating window stayed there. I could move mouse cursor over the edges that it disappears, pressing FN+L it opened again and my text was still there. Now the text is sometimes deleted - sometimes not. Tiny idea: is this floating window suddenly app based? Meaning: if Pages is open, I put in text, close it, press FN+L again: text stays there. If I meanwhile switch to Numbers FN+L opens a complete new window, instead, maybe?
  2. I encounte another big issue with this: suddenly, the activated apps do react on the key input "L" or "FN+L". My action should open the window, instead I am changing things in the background of that App! I got already overwritten cells in Numbers calculation or weird behavior in Unity. Maybe I go back to the last BTT version for some time?
4

this FN+L thing really sounds a lot like secure input mode is active - it can also be active only in specific apps

You can try going back to the previous version but at least this Fn+L issue doesn't sound like it is related to the BTT version

5

Just had a look into the BTT action steps: the "close if click outside" is activated - but not "close when moving mouse away" - but actually BTT is just doing this: closing if I move the mouse away. :confused:

More details: the window now disappears if I move the mouse cursor on the edges already. I chose big edges (around 1-2 cm). Before the update, I clicked there to move the window, now the window disappears super fast, deleting information inside most times. I am unable now to move the window anywhere on the screen.
Another new problem: Hitting FN+L shows sometimes up the window for some milliseconds. Pressing a second time it might stay there.

This issue is since yesterday after I installed your updates several times. I will look into this of course.

How can I send you that action? Or do I have to send a whole file for all?

6

best right-click the menu, then choose the export to file option

7

Linguee_FN+L.bttpreset (25.2 KB)

Thank you for investigating ! :slight_smile:

8

Ah, at least parts of your issue can be explained by this "Hover End" action:

image
image3372×2216 474 KB
u

Deleting this should help a lot.

There was an issue with previous versions that caused hover end actions to be ignored in certain situations - because of this it probably worked so far

1 Like