| MIL 10 Reference
| Customize Help
| Save Settings

MbufGetHookInfo



See also
Availability
Available in MIL-Lite
Available in MIL

Available on Windows
Available on Linux

Partially supported on:
Partially supported on Host system
Partially supported on Matrox CronosPlus
Partially supported on Matrox GPU processing driver
Partially supported on Matrox GigE Vision driver
Partially supported on Matrox IEEE 1394 IIDC driver
Partially supported on Matrox Orion HD
Partially supported on Matrox USB3 Vision driver (requires Update 19)
Partially supported on Matrox Vio

Fully supported on:
Fully supported on Matrox Iris GT
Fully supported on Matrox Morphis
Fully supported on Matrox Morphis QxT
Fully supported on Matrox Radient eCL
Fully supported on Matrox Radient eV-CXP
Fully supported on Matrox Solios eA/XA
Fully supported on Matrox Solios ecl/xcl/ev-cl

For any information regarding a MIL system added during a MIL Update, see the MIL system’s release note

Available on Non-Matrox computer
Available on Matrox 4Sight-X
Available on Matrox 4Sight GP
Available on Matrox Supersight
function map Function map
Examples
None.
Synopsis
Get information about a hook event.
Syntax
MIL_INT MbufGetHookInfo(
MIL_ID EventId, //in
MIL_INT64 InfoType, //in
void *UserVarPtr //out
)
Description

This function allows you to get information about the event that caused the hook handler function to be called. MbufGetHookInfo() should only be called within the scope of a buffer hook-handler function (see MbufHookFunction()).

Note that this function reference has not been updated for a MIL system added during a MIL update. Refer to the MIL system's release note to see which MIL system’s documentation you should use in its place and any possible differences.
Parameters
This function is not supported on the selected boards.
This function reference has not been updated for the selected MIL system. To show the content of this page, choose a second MIL system; refer to the MIL system's release note to see which MIL system’s documentation to choose and any possible differences.
Parameters
EventId

Specifies the buffer event identifier received by the hook-handler function (see MbufHookFunction()).

InfoType

Specifies the event type and the type of information about the event to return.

See the Parameter associations section for possible values that can be specified.

UserVarPtr
Accepts the address of one of the following (see the Parameter associations section for specifics on which is expected):
  • MIL_DOUBLE
  • MIL_ID
  • MIL_INT

Specifies the address in which to write the requested information.

See the Parameter associations section for possible values that can be returned.

The table below lists possible values for the InfoType parameter and possible values returned to the UserVarPtr parameter.

Unless otherwise specified, the following values require that you pass the UserVarPtr parameter the address of a MIL_INT.

function map For the event type
CollapseInfoType Description
UserVarPtr
- Possible values returned
Collapse M_MODIFIED_BUFFER +

Retrieves information about a modified buffer type of event. This event occurs if the hook-handler function was hooked using MbufHookFunction() with M_MODIFIED_BUFFER.


You must specify a combination value from the following table:
(summarize)
Combination constants for M_MODIFIED_BUFFER.

You must add one of the following values to the above-mentioned value to set the type of information to return.

function map For the modified buffer type of event
CollapseInfoType Description
MIL system-specific
tooltip (†)
UserVarPtr
- Possible values returned
Collapse M_BUFFER_ID

Retrieves the MIL identifier of the modified buffer.

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse UserVarPtr data type info

Data type: MIL_ID

a b c d e f g h i j k l m n o p q r s
Collapse M_GRAB_TIME_STAMP

Retrieves the time the event generated service request, in secs. The time can be used to see if a frame has been missed since the last time stamp.

(summarize)
f g h j k l m p q r
Collapse UserVarPtr data type info

Data type: MIL_DOUBLE

f g h j k l m p q r
Collapse M_MOVED

Returns whether the buffer modification event was triggered by a move operation performed by MbufChildMove(); that is, the buffer is a child buffer and its X/Y offset was changed.

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_NO

Specifies that the buffer modification event was not triggered by a move operation.

a b c d e f g h i j k l m n o p q r s
Collapse M_YES

Specifies that the buffer modification event was triggered by a move operation.

a b c d e f g h i j k l m n o p q r s
Collapse M_REGION_OFFSET_X

Retrieves the X-offset of the modified region (of the buffer).

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_REGION_OFFSET_Y

Retrieves the Y-offset of the modified region (of the buffer).

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_REGION_SIZE_X

Retrieves the width of the modified region (of the buffer).

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_REGION_SIZE_Y

Retrieves the height of the modified region (of the buffer).

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_RESIZED

Returns whether the buffer modification event was triggered by a resize operation performed by MbufChildMove(); that is; the buffer is a child buffer and its X/Y size was changed.

(summarize)
a b c d e f g h i j k l m n o p q r s
Collapse M_NO

Specifies that the buffer modification event was not triggered by a resize operation.

a b c d e f g h i j k l m n o p q r s
Collapse M_YES

Specifies that the buffer modification event was triggered by a resize operation.

a b c d e f g h i j k l m n o p q r s
Return value
The returned value is M_NULL if successful. If the operation fails, a non-null (!M_NULL) value is returned.
Compilation information
Header Include mil.h.
Library Use mil.lib.
DLL Requires mil.dll.
MODIFIED BUFFER BUFFER ID GRAB TIME STAMP MOVED NO YES REGION OFFSET X REGION OFFSET Y REGION SIZE X REGION SIZE Y RESIZED NO YES