Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2023-02-26 Thread ydld1pw02
Any progress on making version xdaliclock 2.44 available as a separate package?

Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-11-27 Thread Larry Doolittle
I can confirm that the xdaliclock 2.46 in Bookworm/testing works nothing like historical copies of the program. In my case, I have an ancient incantation buried in my .xsession file /usr/bin/xdaliclock -noseconds -nocycle -builtin1 -bg steelblue -fg black -geom -0-0 and the new xdaliclock

Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Jamie Zawinski
Congrats, you are well on your way to understanding that Linux is a trash fire all the way down! On Sep 26, 2022, at 11:07 AM, Stefan Monnier wrote: > > Oh, it's worse: I installed `picom` which made the opacity slider work, > but that affects the whole window, whereas I only want the

Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Jamie Zawinski
Less snarkily: none of these things can or will be fixed. Adapting xdaliclock to more modern toolkits in order to have fully scalable antialiasing and a real GUI for preferences has some other side effects. If you want to party like it's 1991, run the code from 1991. It still exists.

Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-26 Thread Stefan Monnier
Oh, it's worse: I installed `picom` which made the opacity slider work, but that affects the whole window, whereas I only want the background to be transparent. Along the way I noticed another problem with the opacity compared to the old code that relied on the "Shape" X11 extension: even if I

Bug#1020460: xdaliclock: New version ignores Xresource settings and can't be made transparent

2022-09-21 Thread Stefan Monnier
Package: xdaliclock Version: 2.44+debian-2 Severity: normal The version of xdaliclock in Debian testing seems to be quite different from the version I've been running for the last ... 20 years(?). The most obvious difference is that it disregards my Xresource settings. But more importantly, I