Skip to content
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

Persistent settings despite changing config file #40

Open
steviator opened this issue Apr 13, 2024 · 3 comments
Open

Persistent settings despite changing config file #40

steviator opened this issue Apr 13, 2024 · 3 comments

Comments

@steviator
Copy link

steviator commented Apr 13, 2024

After adding some windows into the list of exceptions, I find that removing them from that list does nothing and there is no documentation anywhere that indicates where the configuration files are stored.

Issue #1 is that the gui configuration doesn't work properly
Issue #2 Is that debugging is hampered by the lack of documentation

I'll now try to remember what the exceptions were that I added and scour my home directory in hopes of finding the elusive secret hidden config file.

@taj-ny
Copy link
Owner

taj-ny commented Apr 13, 2024

the gui configuration doesn't work properly

What exactly doesn't work? Any changes should be applied immediately when you click Apply.

The configuration is stored in ~/.config/kwinrc in the [Effect-blurplus] group.

@steviator
Copy link
Author

Steps to reproduce:

  1. Add window class to list
  2. Refresh force-blur (by uncheck -> apply -> check -> apply process)
  3. Observe blurring exception
  4. Remove window class from list
  5. Refresh force-blur again
  6. Observe blurring exception is still in place
  7. Reboot
  8. Observe blurring exception is still happening
  9. Profit!

@taj-ny
Copy link
Owner

taj-ny commented Apr 13, 2024

Refresh force-blur (by uncheck -> apply -> check -> apply process)

What exactly are you unchecking? Clicking OK or Apply in the effect configuration UI is enough. Are you modifying the file?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants