Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: jcompton
« on: October 18, 2005, 11:15:10 AM »

The implications of that being:

- Unlike a regular state label, you _can_ re-use an I_C_T(2) "label."

- However, doing so has implications--namely, that once an interjection with the label is used, the global will be tripped, so none of the other interjections using that label can be seen. This can, potentially, be used to your advantage.
Posted by: Tess
« on: October 18, 2005, 11:12:13 AM »

Wonderful!  That's what I suspected--thank you!

Tess
Posted by: CamDawg
« on: October 18, 2005, 10:59:05 AM »

I_C_T sets and checks for a global variable. WeiDU adds this automatically--the global has the same name as your I_C_T state--so you shouldn't have to worry about adding a 'no repeat' check. Try compiling some I_C_T .d code and look at the resulting dialogue.
Posted by: Tess
« on: October 18, 2005, 10:48:01 AM »

When I'm using INTERJECT_COPY_TRANS, do I need to code it to change the state so that the interjection can't happen again, in the case of a multiple install or whatnot?  Or, if I'm understanding correctly, does the very nature of the command and the copying of the existing states and transitions and whatnot render this unnecessary?

I'm working off some examples and the WeIDU documentation right now and while it's made clear that this needs to be done when using INTERJECT, it isn't mentioned for INTERJECT_COPY_TRANS.

Thanks!

Tess