Open spiritualgeek opened 10 months ago
Update: It appears to be LanguageTool for desktop that is causing this. I have logged a bug with them, but perhaps you have a workaround?
Thanks for the update. LanguageTool is likely adjusting one of the accessibility parameters to read text from browsers. I don't have a workaround at this time.
Thanks for the update. LanguageTool is likely adjusting one of the accessibility parameters to read text from browsers. I don't have a workaround at this time.
Thanks. I logged an issue with them. Will keep you posted on what they say
For what is worth, I had the same issue with LanguageTool and I solved it with the same fix in other Rectangle (OSS) issues (replacing Rectangle
with Hookshot
):
defaults write com.knollsoft.Hookshot systemWideMouseDown -int 1
Then restarting both apps solved the issue.
@cgrs Thanks! I'm glad you pieced that together since I didn't.
Dear @cgrs, @rxhanson,
I find myself struggling to comprehend the correlation between Hookshot and the fix?
I have reviewed the mentioned issue and must confess that I'm lost :)
I attempted LanguageTool for assistance. However, their support is not great
Thanks
@spiritualgeek Hookshot is built upon Rectangle, so it has the same open-source code at the base. Given that there was a fix for Rectangle with a similar issue, and it was solved there setting that option, I assumed that Hookshot would behave the same way, just updating the reference to the right settings section.
@rxhanson correct me if I'm wrong 😅
Thanks
Could you possibly guide me to a page on an Apple website that outlines the distinction between the two methods?
I'm curious
@spiritualgeek Using this terminal command is setting an internal flag in Rectangle Pro:
defaults write com.knollsoft.Hookshot systemWideMouseDown -int 1
(Hookshot is the old name of Rectangle Pro)
The two different ways that this works is due to a bug with macOS and 3rd party applications where some apps would freeze because of Rectangle/Pro listening to click events. The default behavior avoids that freeze, but causes some issues like this one with LanguageTool.
@rxhanson In this case it seemed like the opposite to me. In other words, everything worked after stopping LanguageTool?
I truly appreciate the feedback. I'm a great fan of R Pro
I have no idea if this is a bug, but my snap targets are all still defined. The hot key is set, but the snap targets just refuse to work.
The same goes for the snap panel
Is there a known bug and a way to fix this?
Thanks