Intuition Loops

[nyteschayde]

So, typically, there is a line in many Intuition loops that looks as follows:

Code: [Select]

Wait (1 << mywin->UserPort->mp_SigBit);

I presume that this is telling the OS that it shouldn't spend cycles on this code until a signal is sent via the window's UserPort via the mp_SigBit. This is typically important since this code is usually in a while(true) or while(trueUntilFlagSet) loop which could easily hog the CPU.

My questions are:

• Are my assumptions about the functionality correct?
• What is the significance of using bit shift operator here. Why 1 << mp_SigBit? Are there other values or messages that are potentially encoded in that signal? What would they be? How can we find them?

[nyteschayde]

Thanks Thomas. You're my guru. So in this case, would you do something like the following if you wanted to wait for intuition based feedback *and* check for CTRL-C?

Code: [Select]

Wait(1 << mywin->UserPort->mp_SigBit | SIGBREAKF_CTRL_C);