View Single Post
  #2  
Old 10-03-2007
Anthony Johnson's Avatar
Anthony Johnson Anthony Johnson is offline
Manager of Product Development
 
Join Date: Jul 2007
Posts: 440
Downloads: 86
Uploads: 4
Thanks: 171
Thanked 899 Times in 288 Posts
Rep Power: 734
Anthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond reputeAnthony Johnson has a reputation beyond repute
Default

You should not call releaseitem() on an item that has already been released (and if you're in a regular object like a Processor and use releaseitem(), you should make sure that the item is not released again by the Processor's normal releasing mechanism. You might accomplish this by destroying the Processor's events, but it is dependent on the point at which you want to do it, and it's not really encouraged to completely override a regular object's normal mechanism). To query whether an item is already released, use getitemstate(). If it's released, it will have either the FRSTATE_READY or FRSTART_MOVEREQUESTED state. You can call holditem() to "unrelease" an item, but you should only use holditem() when it is in the FRSTATE_READY state, and not in either of the other two states. Also refer to the FixedResource object's documentation in the user manual for a detailed description of the steps and states a flowitem goes through in a FixedResource.
Reply With Quote