On Thu, 17 Sep 2020 01:13:06 +0200 Axel Beckert wrote:

[...]
> Francesco Poli wrote:
[...]
> > Well, I would call it a dialog window, since I have to click on the OK
> > button, in order to (cleanly) close it...
> > Please see the attached screenshot (or, rather, "windowshot").
> 
> Ok, I guess that's heavily depending on the notifyd being used. I've
> seen notification in many different styles. There are e.g. GNOME and
> KDE on the fancy side and dunst on the very simplistic side.

I this can be useful to know, I use Fluxbox...

> 
> The content is what I'd expect in a notification.
> 
> And yes, upon start it shows you the current state. Maybe I should add
> an option or so to disable this.

It could be nice, but it's not on the top of my priority list...

[...]
> > By looking at the code, it seems that the complaint is generated
> > because some exception is caught:
[...]
> > Does this ring some bell?
> 
> Not really. Load of the code is borrowed from code examples of the
> libraries or from fdpowermon and tweaked until it did what I wanted.
> So I don't have really an idea what exactly
> "Glib::Object::Introspection->setup" does and which reasons may exist
> for it to fail. I just know it's needed to make this run.

Well, that seems to be the direction in which the investigation has to
be pushed...

[...]
> > Please ping me, when the new version is in Debian testing (or, at
> > least, in unstable): I will give it a try.
> 
> Will do.

Thanks.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgpXEimfFX0Xq.pgp
Description: PGP signature

Reply via email to