Wojtek Lerch wrote:
Talking to a Photon on another node is trivial – just pass the full
path to the appropriate Photon device to PtInit() or, even simpler, set
the PHOTON environment variable before doing the usual Photon
Ok, so say I have a process running on node 2. You press a button on
application. If, instead of having photon run on node 2 as /dev/photon,
had photon running on node 2 as //1/dev/photon, then would my events
keyboard) go to photon on node 1? Would this be intercepted
by an application on node1 that has a text widget in focus?
What is much more tricky is to have one process talk to two Photons at
the same time. If I understand you correctly, you want your proram to
read key events from one Photon and then emit them into another – is
Doesn’t have to be if the above would work.
If it is, then I think the easiest solution is to use two processes and
have one send keys to the other. If you want to keep them as one
program that forks, remember to call fork() before initializing Photon
Two process would be fine as long as it works. How do node2 process
send keys to node1 process and make it appear as a actual keyboard
event (not a normal QNX message).
Thanks for your help so far.
Wojtek Lerch (> email@example.com> ) QNX Software Systems Ltd.
I need to have an Photon application running on one node send
an key event to another Photon application running on a different
node. Does anyone know how to do this? Think of it as a virtual
keyboard running on the secondary node that when the user presses
a key ( like keypad key “2” ), the 2 would appear on the currently
focused widget in the application running on the primary node.
I would like to fake out Input somehow so that my application running
on node 2 sends a key press event to the Input process on node 1, that
way the application code on node 1 thinks it came from the keyboard
and not another application.