Thanks Sasha and Peter<br>Anybody know what software is sending the signal now?<br><br>Gonzalo<br><br><br><div class="gmail_quote">On Thu, Oct 14, 2010 at 6:38 AM, Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com">pbrobinson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Thu, Oct 14, 2010 at 9:27 AM, Sascha Silbe<br>
<<a href="mailto:sascha-ml-reply-to-2010-3@silbe.org">sascha-ml-reply-to-2010-3@silbe.org</a>> wrote:<br>
> Excerpts from Gonzalo Odiard's message of Wed Oct 13 17:33:50 +0200 2010:<br>
><br>
>> bus.add_signal_receiver(my_func,<br>
>> dbus_interface="org.freedesktop.Hal.Device",<br>
>> signal_name="PropertyModified")<br>
><br>
> HAL has been deprecated [1] and will not be available anymore at some<br>
> point in the future, so I advise against relying on it.<br>
><br>
> I don't know what the best way to listen to an ebook switch is. acpid<br>
> might be worth a look:<br>
<br>
</div>Most distros don't use acpid either<br>
<div class="im"><br>
>>> In addition to rule files, acpid also accepts connections on a UNIX<br>
>>> domain socket (/var/run/acpid.socket by default). Any application may<br>
>>> connect to this socket. Once connected, acpid will send the text of all<br>
>>> ACPI events to the client. The client has the responsibility of<br>
>>> filtering for messages about which it cares. acpid will not close the<br>
>>> client socket except in the case of a SIGHUP or acpid exiting.<br>
><br>
> Asking for advice on devkit-devel [2] might be a good idea as well.<br>
> UPower already has a LidIsClosed property (and sends property change<br>
> notifications [4]) so it might be straightforward to add support for<br>
> ebook switches.<br>
<br>
</div>I think this should be an input event, I think in most cases this is<br>
how input from lid switches and the like are handled across most<br>
things now.<br>
<br>
Peter<br>
_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
</blockquote></div><br>