showing mouse pointer position when pressing Ctrl interferes with Fcitx about muffin HOT 22 OPEN

@lhmouse This is not an issue with Cinnamon but a limitation with X11. You can verify by using the other Ctrl key if you have one but also using and releasing another key modifier before Ctrl (i.e. pressing Alt, then Ctrl, then releasing Alt while still holding down Ctrl) will also free the Ctrl key combo for your regular modifiers.

To workaround this (other than with the key modifiers trick), you can map the "Show position of pointer when..." option to another key that does not interfere with your regular operations, such as the right Ctrl key. This option is only available via dconf (/org/cinnamon/muffin/locate-pointer-key) or gsettings (org.cinnamon.muffin locate-pointer-key) though.

from muffin.

@lhmouse This is not an issue with Cinnamon but a limitation with X11. You can verify by using the other Ctrl key if you have one but also using and releasing another key modifier before Ctrl (i.e. pressing Alt, then Ctrl, then releasing Alt while still holding down Ctrl) will also free the Ctrl key combo for your regular modifiers.

Yes looks like so.

I just switched from MATE to Cinnamon yesterday. On MATE, pressing left Ctrl with that option turned on could cause textboxes to lose focus (reported here) but certainly it did not prevent me from switching IMEs.

from muffin.

So possibly something in the key down sequence that changed? Hmm, if this is an issue, it would most likely be in muffin I think but I'm not sure if anything can be done in the short-term.

from muffin.

I wonder if changing the locate pointer action to occur on the key up is possible? I'm not sure but it might be worth a look.

from muffin.

That is already what it behaves; the ripple effect is played when the left Ctrl key is released. However, some inputboxes lose focus as soon as the Ctrl key is pressed.

Known to work (inputbox does not lose focus)

1. Opera
2. HexChat
3. Thunderbird
4. Menu

Known to fail (inputbox loses focus, which makes copying with Ctrl-C impossible)

1. Fcitx (pressing left Ctrl deactivates the IME)
2. Nemo (only when renaming a file)
3. gufw (when adding rules)

from muffin.

A few notes here:

1. I've worked around this by pre-pending the Ctrl key press with an Alt key press but any other key would work (i.e. pressing Alt, then pressing Ctrl, then releasing Alt while still holding down Ctrl). This combination prevents the location trigger from activating.

2. This issue is actually resolved in Wayland. While it's still fairly far away, this issue will go away some day (for what that's worth 😅). Link to the blog post with the Wayland update.

from muffin.

To be honest 'it doesn't work in X' sounds unsatisfactory. There are applications where it works perfectly (web browsers for example) and I suspect it should work everywhere.

from muffin.

To be honest 'it doesn't work in X' sounds unsatisfactory. There are applications where it works perfectly (web browsers for example) and I suspect it should work everywhere.

I can verifiably say it does not work in my browsers in X11:

• If you type in the address bar and it opens a dialog with history or bookmarks and hit the Ctrl key to trigger the location, it cancels out the address bar entirely.
• I often even have issues with Ctrl+Enter with addresses in the address bar unless I use the first item in my note above.

Please double check which input fields are and are not having issues because it is absolutely a limitation of X11.

from muffin.

That doesn't happen on my browser, Opera 104.0.4944.36. Does it happen on Chromium or Firefox? Or I suspect Opera has customized their address bar somehow?

from muffin.

That doesn't happen on my browser, Opera 104.0.4944.36. Does it happen on Chromium or Firefox? Or I suspect Opera has customized their address bar somehow?

Opera is the only browser I haven't used in the past decade so I'm not sure what they're doing. 😅
They must be somehow drawing the address bar differently. Test with a different Chromium-based or Firefox-based browser and you'll see the issue clearly. Definitely test with the next version of Mint in a Wayland session and you'll see the difference as well. (It's one of the first things I tested myself.)

from muffin.

Opera is the only browser I haven't used in the past decade so I'm not sure what they're doing. 😅 They must be somehow drawing the address bar differently. Test with a different Chromium-based or Firefox-based browser and you'll see the issue clearly. Definitely test with the next version of Mint in a Wayland session and you'll see the difference as well. (It's one of the first things I tested myself.)

Thanks. I shall note this.

When will the next version of Mint be available, within this year? I don't mind whether it's beta whatsoever. We don't have Mint in production environments.

from muffin.

When will the next version of Mint be available, within this year?

Per this blog post, December 2023 is the current target.

from muffin.