-
Notifications
You must be signed in to change notification settings - Fork 21
icons resetting #1
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
Comments
Thank you, you are awesome. I would have never found such an estoeric fix without your assistance, Thanks again. |
Perhaps we should adapt this to the docs (as a FAQ/Note or whatever). |
On Thu, 10 Sep 2020 at 8:28:40 -0700, Roman Dobosz wrote:
Perhaps we should adapt this to the docs (as a FAQ/Note or whatever).
Good idea. Would you like to write a patch to the window maker
homepage?
https://github.com/window-maker/window-maker.github.io
|
@crmafra I've filled an issue for it window-maker/window-maker.github.io#11 just to not forget :) |
The only thing I can think of is that it is connected with saving session. Do you use saving session for wmaker? |
Hi, been messing with this. |
Perhaps this is strictly connected with Seamonkey, which might happen to manage its own icon by itself. Do you observe such a behavior on other programs as well? Can you provide the names? |
xpaint is another example. |
I have tested steps described above with xpaint-2.10.2 and it's seems to work. Icon firmly stays changed. |
Didn't hear from @brightersun99 about this issue for couple of months now. I guess we can close it, otherwise it could be reopened. Note, that documentation issue is under another repo. |
I am running the latest windowmaker.
I have some icons saved to my dock/clip, for launching things. I have set their icons to custom icons
And it works until I launch the program, then it reverts back to its original icon. Right clicking and editing it shows the path is still set to my custom icon, I can change it and it will still revert again until I do something with that program.
Seems this has been a bug since around 2004, fix it please?
The text was updated successfully, but these errors were encountered: