Quote:
Originally Posted by FDD
The hanvon source is available in the onyx-intl-toolchain, pkgs/tslib/plugins directory. The hanvon digitizer really uses Wacom's IDSV4 protocol, so that plugin isn't badly needed, but there it is 
I'm not sure I understand your second sentence...  you are trying to make gui_shell do things from the shell (or script etc.)? By the way I didn't look what kind of events they (gui_shell and system_manager) signal to each other over the DBUS  |
ah - thx - I had overlooked that directory...
I originally was talking about problems extending onyx's versions of gui_shell and system_manager.
Thus the second part was about _using_ the extended functionality in Onyx's firmware. New applications could use the described socket, but gui_shell would not.
The next idea was a daemon using the DBus to trigger events in gui_shell and system_manager... but so far I had no luck.
The only signals that are broadcast on the system DBus (eavesdropped with dbus-monitor --system) seem
* 'Idle'
* Volume-related signals,
* starting/stopping of applications,
* aboutToSuspend
* and when a new wifi connection was established.
But simply reproducing the signals on the bus by use of dbus-send did not elicit responses, so I assume that applications pay heed to the sender... so I guess that you'd have to spoof the sender. (currently don't know how to do that)