---- "Sl�vek Banko" <slavek.banko@...> wrote: 
> On Sunday 09 of March 2014 13:18:37 E. Liddell wrote:
> > On Sun, 9 Mar 2014 03:07:30 +0000 (GMT)
> >
> > Michele Calgaro <michele.calgaro@...> wrote:
> > > > For input event devices such periodic rescan now represent dbus call to
> > > > check the status of switches. Find ways to solution listed as 1) would
> > > > be good.
> > >
> > > I also think we should investingate option 1), even though I have no idea
> > > how to do that.
> >
> > I *think* we need to set up to receive notification signals from dbus, but
> > most of the available documentation and examples are beyond my C
> > programming weight class.  The obvious place to start is dbus's own docs
> > ( http://www.freedesktop.org/wiki/Software/dbus/#index4h1 ). There's also
> > what seems to be an extensive example of signal creation and capture at
> > http://maemo.org/development/training/maemo_platform_development_content/pl
> >ain_html/node6/
> >
> > E. Liddell
> >
> 
> You need to first make a list of "what to watch" and then find out "who will 
> watch." We can not receive dbus signals until it is no one who send these 
> signals :)
> 
> Already when I implemented the reading switches on the input event devices, I 
> considered that monitoring could be carried out in tde_dbus_hardwarecontrol 
> that would send dbus signals. But that would require first change way to 
> refresh informations in tdehw-lib.
> 
> -- 
> Slavek
> 

At least from my original post on this thread, we know what it is looking at on my box. Is there some way I can dump additional information that would be helpful in this regard?

--
David C. Rankin, J.D.,P.E.