![]() |
Re: Dbus scripts settings and proximity sensor
nope, sysfs is dynamically created as you read it. inotify doesnt work there.
NEXT! UDEV? |
Re: Enabling right click with Dbus scripts and proximity sensor
And this all leads me back to the start!
While there is an entry in sysfs for the proximity sensor AND it is seen by HAL, there is nothing that reacts to it (PLEASE correct me if I am wrong). So no use if a dbus triggered script, no use of HAL events nothing. just nothing. Which blows. So this should also lead you too, to two possibilities. we must conclude: 1. I am not sure what interprets the touch creen input (evinput, hildon, xorg?) however I believe it would be EXTREMELY easy to alter the source code to somthing like: Code:
when click detected: Does any one have any thoughts on option 1? |
Re: Enabling right click with Dbus scripts and proximity sensor
Hi vi_, the gpio exposes an interface to interact with via dbus. It means that it emits some signals and provide some methods to interact with. How you cope with that, depends on the language/tools you use. AFAIK both Qt and Gtk offers the chance to play with dbus (obviously). Python offers a native way to interact with dbus and there are Python bindings for Qt, too.
HTH your further researches EDIT: did you find http://talk.maemo.org/showthread.php?t=62198 for example? And this one: https://bugs.maemo.org/show_bug.cgi?id=7070 useful, too... |
Re: Enabling right click with Dbus scripts and proximity sensor
haha, good morning, start working stop hacking now. If you take a look at the code - I think autogenerated but I am not expert enough - of proximityclock, it makes it the hard way polling the gpio related file every 10ms
|
All times are GMT. The time now is 21:21. |
vBulletin® Version 3.8.8