Differences

This shows you the differences between two versions of the page.

--- en:docs:fapi:viomodewait [2021/09/05 04:48] – created prokushev
+++ en:docs:fapi:viomodewait [2021/11/04 12:36] (current) – prokushev
@@ Line 1: / Line 1: @@
+{{page>en:templates:fapiint}}
+====== VioModeWait ======
 This call allows a graphics mode application to be notified when it must restore its video mode, state, and modified display adapter registers. The return from this function call provides the notification.
-==Syntax==
+===== Syntax =====
+<code c>
  VioModeWait (RequestType, NotifyType, Reserved)
+</code>
-==Parameters==
+===== Parameters =====
-;RequestType (USHORT) - input : Application request event. RequestType = 0 indicates the application wants to be notified at the end of a pop-up to restore its mode. RequestType = 0 is the only event supported by VioModeWait.
-;NotifyType (PUSHORT) - output : Address of the operation to be performed by the application returning from VioModeWait. NotifyType = 0, indicating restore mode, is the only type of notification returned.
-;Reserved (USHORT) - input : Reserved word of 0s.
-==Return Code==
+  * RequestType (USHORT) - input : Application request event. RequestType = 0 indicates the application wants to be notified at the end of a pop-up to restore its mode. RequestType = 0 is the only event supported by VioModeWait.
-;rc (USHORT) - return:Return code descriptions are:
+  * NotifyType (PUSHORT) - output : Address of the operation to be performed by the application returning from VioModeWait. NotifyType = 0, indicating restore mode, is the only type of notification returned.
-* 0  NO_ERROR
+  * Reserved (USHORT) - input : Reserved word of 0s.
-*421 ERROR_VIO_INVALID_PARMS
-*422 ERROR_VIO_FUNCTION_OWNED
+===== Return Code =====
-*423 ERROR_VIO_RETURN
-*424 ERROR_SCS_INVALID_FUNCTION
+rc (USHORT) - return:Return code descriptions are:
-*428 ERROR_VIO_NO_SAVE_RESTORE_THD
-*430 ERROR_VIO_ILLEGAL_DURING_POPUP
+  * 0  NO_ERROR
-*465 ERROR_VIO_DETACHED
+  *421 ERROR_VIO_INVALID_PARMS
-*494 ERROR_VIO_EXTENDED_SG
+  *422 ERROR_VIO_FUNCTION_OWNED
+  *423 ERROR_VIO_RETURN
+  *424 ERROR_SCS_INVALID_FUNCTION
+  *428 ERROR_VIO_NO_SAVE_RESTORE_THD
+  *430 ERROR_VIO_ILLEGAL_DURING_POPUP
+  *465 ERROR_VIO_DETACHED
+  *494 ERROR_VIO_EXTENDED_SG
+===== Remarks =====
-==Remarks==
 At the completion of an application or hard error pop-up (reference VioPopUp), OS/2 notifies the session that was originally interrupted for the pop-up to restore its mode. The return from this function call provides that notification. The thread that issued the call must perform the restore and then immediately re-issue VioModeWait.
@@ Line 32: / Line 42: @@
 When an application issues VioModeWait, it is also required to issue VioSavRedrawWait to be notified at screen switch time to perform a full save or restore (reference VioSavRedrawWait. Two application threads must be dedicated to performing these operations.
-==Bindings==
+===== Bindings =====
-===C===
-<PRE>
+====C====
+<code c>
 #define INCL_VIO
@@ Line 44: / Line 55: @@
 USHORT  rc;            /* return code */
-</PRE>
+</code>
-===MASM===
+====MASM====
-<PRE>
+<code asm>
 EXTRN  VioModeWait:FAR
 INCL_VIO            EQU 1
@@ Line 57: / Line 68: @@
 Returns WORD
-</PRE>
+</code>
 [[http://www.edm2.com/index.php/VioModeWait_(OS/2_1.x)]]
+{{page>en:templates:fapi}}