Difference between revisions of "NET:LavishVMAPI.Frame.Wait"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
See [[NET:Concepts:Frame Locking|Frame Locking]]. | See [[NET:Concepts:Frame Locking|Frame Locking]]. | ||
| − | + | Wait causes a thread to yield execution until the ''next frame'' begins. Retaining a frame lock following a call to Wait is optional, via the bLock parameter. If lock is retained, there must be one unlock call per successful lock call. '''Wait should not be used in a thread that already has frame lock acquired''', as this results in deadlock (it is logically impossible). | |
=== Reference Library === | === Reference Library === | ||
Latest revision as of 18:42, 19 January 2007
Contents
Overview
See Frame Locking.
Wait causes a thread to yield execution until the next frame begins. Retaining a frame lock following a call to Wait is optional, via the bLock parameter. If lock is retained, there must be one unlock call per successful lock call. Wait should not be used in a thread that already has frame lock acquired, as this results in deadlock (it is logically impossible).
Reference Library
Fully Qualified Name
- LavishVMAPI.Frame.Wait
- LavishVMAPI namespace
- Frame class
- Wait function
- Frame class
Declaration
static public void Wait(bool bLock);
Parameters
- [In] bool bLock
- If true, retains an acquired frame lock. If false, the implicit frame lock is released.
Return Value
None
