no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| Next revision | |||
| — | en:docs:fapi:vioscrunlock [2018/09/01 09:53] – created prokushev | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | |||
| + | This call releases ownership of (unlocks) the physical display buffer. | ||
| + | |||
| + | ==Syntax== | ||
| + | | ||
| + | |||
| + | ==Parameters== | ||
| + | ;VioHandle (HVIO) - input : Reserved word of 0s. | ||
| + | |||
| + | ==Return Code== | ||
| + | rc (USHORT) - return | ||
| + | Return code descriptions are: | ||
| + | * 0 NO_ERROR | ||
| + | * 367 ERROR_VIO_UNLOCK | ||
| + | * 430 ERROR_VIO_ILLEGAL_DURING_POPUP | ||
| + | * 436 ERROR_VIO_INVALID_HANDLE | ||
| + | * 465 ERROR_VIO_DETACHED | ||
| + | * 494 ERROR_VIO_EXTENDED_SG | ||
| + | |||
| + | ==Remarks== | ||
| + | This call releases the screen lock that is set by VioScrLock. The VioScrUnLock call must be issued by a thread in the same process as the thread that issued VioScrLock. | ||
| + | |||
| + | ===Family API Considerations=== | ||
| + | Some options operate differently in the DOS mode than in the OS/2 mode. Therefore, the following restriction applies to VioScrUnLock when coding in the DOS mode: | ||
| + | |||
| + | The status always indicates the unlock is successful (return code = 0). | ||
| + | |||
| + | ==Example Code== | ||
| + | === C Binding=== | ||
| + | <PRE> | ||
| + | #define INCL_VIO | ||
| + | |||
| + | USHORT | ||
| + | |||
| + | HVIO | ||
| + | |||
| + | USHORT | ||
| + | </ | ||
| + | |||
| + | ===MASM Binding=== | ||
| + | <PRE> | ||
| + | EXTRN VioScrUnLock: | ||
| + | INCL_VIO | ||
| + | |||
| + | PUSH | ||
| + | CALL | ||
| + | |||
| + | Returns WORD | ||
| + | </ | ||
| + | |||
| + | |||
| + | |||
| + | ====== Note ====== | ||
| + | |||
| + | Text based on [[http:// | ||
| + | |||
| + | {{page> | ||
| + | |||