I have used 1 Finger Force Click to close tabs in all apps and have never experienced a problem until about a week or so ago it stopped working. Forcing 1 Finger click still closes tabs in other apps i.e. Firefox Nightly etc but does nothing in Finder.
Oddly 2 Finger Force Click works and closes the tab and so does 3 Finger Force Click however I uses those for other triggers else where and would prefer to keep the force 1 finger for finder. Right now i am having to resort to using 3 finger hold for long time i.e. use IIRC 2 seconds just for Finder tabs/then close window i use script that when 1 tab quits Finder.
Anyone else experience this phenomenon or know what is going on? It is just strange that it only problem is Finder tabs and only 1 Finger Force Click and it not like it is doing a system function (from what i can tell nor is it doing a BTT function which i know for fact bc I checked)
Any help would be appreciated.
how do you have the force click to close tabs configured?
just with a Named Trigger called Close Tab which is just an alias for COMMAND+W which makes this even stranger because using that shortcut CMD+W by itself works and closes tab like it always has, however if it is put into a 1 finger force click trigger it does not work. Same named trigger and CMD+W (same thing but tried both just because) work for all other trigger force touch included 2 finger, 3 finger etc, long touches, double clicks, but just NOT 1 FINGER FORCE CLICK haha so wierd! works every other app but Finder nope but the shortcut itself still works so im scratching my head vigorously. Any help would be appreciated because it messes my workflow up for finder to be different from every other app ; ) wink
okay well i got my answer.....sort of. Didn't realize/see that the new keyboard shortcut implementation was in BETA still, didnt see that or guess overlooked it, thought it was pretty much standard @ this point-even though I am running latest up to date beta. Anyways once saw the Beta wording next to it in setting decided to give it a try and toggled it off and golly it works just like normal. Wierd bug. And since I dont really know at this point/notice any noticeable benefits at this very second-im sure three are TONS and I will switch back to it soon and duh it will be default soon enoigh but at this very second my workflows all seem to work and no kinks-was experiencing some other little kinks that are now gone like with the hyper key and implentations I was using via Karbinder Elements-they are cleared up npw.
So for anyone having any issues give toggling off the new implementation a try-if it okay and wont do too much dmage or hold back what we can do-let us know Andreas. And thanks as always best app dev and best app much lovve good luck
the new keyboard shortcut implementation has been the default for ~10 years, it is not beta.
However it can also not influence this as it only relates to keyboard shortcut triggers, not keyboard shortcuts sent via a trackpad gesture. This is most likely a coincidence. I‘d highly recommend to enable this again.
Sorry used wrong terminology my apologizes. I meant to say: Use modern trigger/action configuration (Beta)
that is what did the trick
that setting only influences the configuration UI, it can also not change the behavior of this (at least once configured)
