-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to click in Open or Save or Save As window in certain apps #31
Comments
For your information, noShadows.bundle works perfect for the pop-up windows, except that there are no dropdown menus for to choose. Nevertheless, it is a great bundle!! Hope to see the newly updated bundle and I won't hesitate to pay for it. Thanks! |
Most likely you should just blacklist Even though all those apps are different they're most likely using the openAndSavePanelService. |
Thanks for the suggestion. I don't know how this works, so I added every possible name in both App_Blacklist and CLS_Blacklist as shown in the screenshot. I tried but got no luck. The issue is still there. |
Im having exactly the same issue! |
Now I switch to "noShadows" plugin, lack of some functionality though. Ive been cool with it. Link attached: or you can find it inside the MacForge. Edit: seems that another method out there: Here's the repo: Here's the documentation wiki. |
Hi W0lfschild,
Thanks for this excellent bundle.
I find that when winBuddy is turned on, any part of Open or Save or Save As window is unclickable in certain apps.
I know that I can block the apps that is not compatible, but it seems to be too many apps have the same disturbing issue. That's why I seek help here.
If any additional info is needed please let me know.
Tested on:
MacOS 10.14.6
MacForge 0.12.2
winBuddy 0.3.1 and winBuddy 0.3.5
Results:
Unclickable:
Safari.app
Preview.app
Numbers.app
Pages.app
Keynote.app
Red Lines Tools.app
,etc.
Clickable:
Google Chrome.app
Keyboard Maestro.app
Notes.app
Scrivener.app
,etc.
Below is the screenshot:
Best,
ZQSO.
The text was updated successfully, but these errors were encountered: