GreResetBounds: Difference between revisions
Created page with "GreResetBounds resets the bounds to their initial values, hex 07FFFFF for the minimum coordinates and hex F800000 for the maximum coordinates. This function must be supporte..." |
mNo edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
GreResetBounds resets the bounds to their initial values, hex 07FFFFF for the minimum coordinates and hex F800000 for the maximum coordinates. | GreResetBounds resets the bounds to their initial values, hex 07FFFFF for the minimum coordinates and hex F800000 for the maximum coordinates. | ||
This function must be supported by the presentation driver. GreResetBounds is called by the function GpiResetBoundaryData, and is used to reset the boundary data for a presentation space or device context pair | This function must be supported by the presentation driver. GreResetBounds is called by the function [[GpiResetBoundaryData]], and is used to reset the boundary data for a presentation space or device context pair. | ||
== Syntax == | == Syntax == | ||
GreResetBounds(hdc, flOptions, pInstance, lFunction) | GreResetBounds(hdc, flOptions, pInstance, lFunction) | ||
== Parameters == | == Parameters == | ||
; hdc (HDC) - input : Device context handle. | ;hdc (HDC) - input: Device context handle. | ||
;flOptions (ULONG) - input: Option flags. | |||
; flOptions (ULONG) - input : Option flags. | :Valid flags are: | ||
Valid flags are: | ::RB_GPI Reset the GPI bounds | ||
::RB_USER Reset the user bounds | |||
;pInstance (PVOID) - input: Pointer to instance data. | |||
;lFunction (ULONG) - input: High-order WORD=flags; low-order WORD=NGreResetBounds. | |||
; pInstance (PVOID) - input : Pointer to instance data. | |||
; lFunction (ULONG) - input : High-order WORD=flags; low-order WORD=NGreResetBounds. | |||
== Returns == | == Returns == | ||
; rc (BOOL) - returns | ;rc (BOOL) - returns: Return code. | ||
On completion, the handling routine must return a BOOLEAN value to indicate success or an error. | |||
On completion, the handling routine must return a BOOLEAN value to indicate success or an error. | TRUE Successful | ||
TRUE Successful | FALSE Error | ||
FALSE Error | Possible Errors Detected: When an error is detected, the handling routine must call WinSetErrorInfo to post the condition. Error codes for conditions that the handling routine is expected to check include: | ||
Possible Errors Detected: When an error is detected, the handling routine must call WinSetErrorInfo to post the condition. Error codes for conditions that the handling routine is expected to check include: | PMERR_DEV_FUNC_NOT_INSTALLED | ||
PMERR_DEV_FUNC_NOT_INSTALLED | PMERR_INV_HDC | ||
PMERR_INV_HDC | |||
== Remarks == | == Remarks == | ||
Hardcopy drivers are required to support only GPI bounds. Display drivers must also support user bounds for the Window Manager. | Hardcopy drivers are required to support only GPI bounds. Display drivers must also support user bounds for the Window Manager. | ||
[[Category:Gre]] | [[Category:Gre]] | ||
Latest revision as of 20:21, 17 January 2020
GreResetBounds resets the bounds to their initial values, hex 07FFFFF for the minimum coordinates and hex F800000 for the maximum coordinates.
This function must be supported by the presentation driver. GreResetBounds is called by the function GpiResetBoundaryData, and is used to reset the boundary data for a presentation space or device context pair.
Syntax
GreResetBounds(hdc, flOptions, pInstance, lFunction)
Parameters
- hdc (HDC) - input
- Device context handle.
- flOptions (ULONG) - input
- Option flags.
- Valid flags are:
- RB_GPI Reset the GPI bounds
- RB_USER Reset the user bounds
- pInstance (PVOID) - input
- Pointer to instance data.
- lFunction (ULONG) - input
- High-order WORD=flags; low-order WORD=NGreResetBounds.
Returns
- rc (BOOL) - returns
- Return code.
On completion, the handling routine must return a BOOLEAN value to indicate success or an error.
TRUE Successful FALSE Error
Possible Errors Detected: When an error is detected, the handling routine must call WinSetErrorInfo to post the condition. Error codes for conditions that the handling routine is expected to check include:
PMERR_DEV_FUNC_NOT_INSTALLED PMERR_INV_HDC
Remarks
Hardcopy drivers are required to support only GPI bounds. Display drivers must also support user bounds for the Window Manager.