Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 18 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 19 hrs ago -
Maemo repository (3)
to Community by torsen - 2 days, 11 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 9 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 15 hrs ago - more...
|
2011-02-25
, 13:29
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#12
|
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:
2. option 2, see first post...
Does any one have any thoughts on option 1?
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:
if proximity is closed
right click
else left click
Does any one have any thoughts on option 1?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
| The Following User Says Thank You to vi_ For This Useful Post: | ||
|
|
2011-03-21
, 06:21
|
|
Posts: 370 |
Thanked: 443 times |
Joined on Jan 2006
@ Italy
|
#13
|
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...
Last edited by jurop88; 2011-03-21 at 07:10. Reason: thread with some hints
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...
Last edited by jurop88; 2011-03-21 at 07:10. Reason: thread with some hints
|
|
2011-03-21
, 07:53
|
|
Posts: 370 |
Thanked: 443 times |
Joined on Jan 2006
@ Italy
|
#14
|
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
NEXT!
UDEV?