Is there a plan to access also the accelerometers through dbus? it seems to me that reading continuously from them without appropriate timing could be heavy for the battery. more, having to do the decoding part from each application who uses the sensor is complicated and error prone, while having a signal for the position change, with x,y,z already decoded would simplify a lot the coding (and encourage it)..<br>
<br>BTW, very good idea and good and readable code<br><br>(i didn't test it, but reading the code i thougth this: shouldn't the lines 55 and 56 be unindented of 1 space? actually they intercept only the first call, and if there is a second call you have to turn it up and then down.. is that wanted? or maybe i just didn't read well the code and it is correct.. in this case just ignore the question :))<br>
<br>roby<br><br><div class="gmail_quote">On Sun, Oct 26, 2008 at 1:28 PM, Michael 'Mickey' Lauer <span dir="ltr"><<a href="mailto:mickey@openmoko.org">mickey@openmoko.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Amazing work! Can we drag it into the 'examples' folder in FSO?<br>
<br>
Btw., note that once we have some missing glue done, we'll have signals<br>
like "EnterArea" and "LeaveArea" for GPS (and more), so use-cases like yours<br>
should be expressable via simple rules in our rules file.<br>
<br>
--<br>
<font color="#888888">:M:<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
Openmoko community mailing list<br>
<a href="mailto:community@lists.openmoko.org">community@lists.openmoko.org</a><br>
<a href="http://lists.openmoko.org/mailman/listinfo/community" target="_blank">http://lists.openmoko.org/mailman/listinfo/community</a><br>
</div></div></blockquote></div><br>