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

Package:
xdaliclock
Source:
xdaliclock
Description:
Melting digital clock
Submitter:
Stefan Monnier
Date:
2023-10-23 14:36:05 UTC
Severity:
normal
#1020460#5
Date:
2022-09-21 21:57:15 UTC
From:
To:
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 was running it with `XDaliClock.transparent: true`,
but with the new code I can't seem to make it transparent.
I tried to play with the opacity slider in the GUI config, but it has no effect
on my system.  That might be due to my window-manager (ctwm) but the
transparency was the main feature which made me use this program, but this
failure makes it pointless.

I reverted to the xdaliclock in Debian stable for now.  Could there be two
builds of `xdaliclock` available, a bit like the `emacs-lucid` and `emacs-gtk`
alternatives?


        Stefan
#1020460#10
Date:
2022-09-26 18:07:11 UTC
From:
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 can use the
"opacity" setting to let me see my windows underneath the clock,
clicking in the background of the clock sends the even to the clock
rather than to the underlying window  :-(


        Stefan
#1020460#15
Date:
2022-09-26 18:30:10 UTC
From:
To:
If you want to party like it's 1991, run the code from 1991. It still exists.
#1020460#20
Date:
2022-09-26 18:23:57 UTC
From:
To:
Congrats, you are well on your way to understanding that Linux is a trash fire all the way down!
#1020460#25
Date:
2022-11-28 04:14:49 UTC
From:
To:
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 understands none of those options.

Also, five minutes of digging revealed no documentation that any of those
features are supported in some other way.

Like Stefan, I reverted to the 2.44 binary that's part of Bullseye,
and that works fine.  I also confirmed that the xdaliclock_2.44+debian-2
source package builds and runs without issue in a Bookworm environment.

If we keep xdaliclock 2.46 in Debian despite Jamie's hostility,
can we at least give it a new name, and keep xdaliclock as
the traditional (2.44) version?

  - Larry

P.S. Can someone fix the Version tag here?  It seems to have been
confused by Stefan reverting to 2.44 before filing the bug report.
This bug actually applies to 2.46 but not 2.44.
#1020460#30
Date:
2022-11-28 04:55:54 UTC
From:
To:
notfound: 2.44+debian-2
found: 2.46-1
thanks

Sorry for the late reply, will try to see how we can revert back to
2.44 with keeping the nice work done by Barak A. Pearlmutter.
#1020460#39
Date:
2023-02-27 02:15:24 UTC
From:
To:
Any progress on making version xdaliclock 2.44 available as a separate package?
#1020460#44
Date:
2023-10-23 14:26:27 UTC
From:
To:
Some people have no clue what software maintenance means.
How pathetic. This thing has not been "improved", it
has been fundamentally broken in 2.46.

So, just took the 2.44 soruces from bullseye, compiled
with a simlpe "make x" and put the binary into /usr/local/bin
and archived the soruces on my side. Problem fixed.

Arno