Intuition On Click Event?

[Thomas Richter]

Originally Posted by bebbo

looks good.

Looks bad. First of all, the signal is triggered once, but if multiple messages are in the port, you will deadlock on a signal that was already cleared. Second, you do not check which signal was received. Third, you miss a check for NULL because you collected a signal from a different port. The 0xf800... something is because you are not running MuForce (do that!) and you try to evaluate a message through a NULL pointer, and thus instead evaluate the interrupt vector base with offset 0. Thus: [code] signals = Wait(...); if (signal & (1UL

[Thomas Richter]

Originally Posted by bebbo

looks good.

Looks bad. First of all, the signal is triggered once, but if multiple messages are in the port, you will deadlock on a signal that was already cleared. Second, you do not check which signal was received. Third, you miss a check for NULL because you collected a signal from a different port. The 0xf800... something is because you are not running MuForce (do that!) and you try to evaluate a message through a NULL pointer, and thus instead evaluate the interrupt vector base with offset 0.

signals = Wait(...);

if (signal & (1UL << windowsignal)) {
 while(msg = GT_GetIMsg(...)) {
   ... handle messsage ...
   GT_ReplyIMsg(msg);
 }
} else if (signal & (othersignalmask)) {
 ...
}

[Sim085]

Thank you for the sample code. This helped me a lot. I have re-organized my code to follow the same structure. The code is more readable like this and while going through the changes I also spotted an issue with how I was managing the second signal mask.

Will read about MuForce.

Originally Posted by Thomas Richter

signals = Wait(...);

if (signal & (1UL << windowsignal)) {
 while(msg = GT_GetIMsg(...)) {
   ... handle messsage ...
   GT_ReplyIMsg(msg);
 }
} else if (signal & (othersignalmask)) {
 ...
}