jhroyer <firstname.lastname@example.org> wrote:
Yes MsgDeliverEvent would be way better since I have to use
How can I get the rcvid it needs ?
I need to find out the rcvid of the channel where PtAppAddInput
adds its callback…
I don’t think you can get a rcvid without sending to yourself…
MsgSendPulse() seems much easier:
struct sigevent sev;
PtPulseArm( NULL, phpulse, &sev ); // Do this once at startup
assert( sev.sigev_notify == SIGEV_PULSE );
MsgSendPulse( sev.sigev_coid, sev.sigev_priority, sev.sigev_code, sev.sigev_value.sival_int );
Previously, Wojtek Lerch wrote in qdn.public.qnxrtp.photon:
BTW Instead of using PtAppPulseTrigger(), you could just look into the
sigevent structure generated by PtPulseArm(), and use a kernel function
like MsgDeliverEvent() or MsgSendPulse(). This requires a bit more
setup but lets you avoid being blocked inside PtEnter().
Wojtek Lerch (email@example.com) QNX Software Systems Ltd.