Skip to main content

MbufHookFunction

BoardSupported
Host SystemPartial
V4L2Yes
Clarity UHDPartial
Concord PoENo
GenTLYes
GevIQPartial
GigE VisionPartial
IndioNo
Iris GTXPartial
Radient eV-CLPartial
Rapixo CLPartial
Rapixo CoFPartial
Rapixo CXPPartial
USB3 VisionPartial

Hook a function to a buffer or container event.

Syntax

void MbufHookFunction(
AIL_ID ContainerOrBufId, //in
AIL_INT HookType, //in
AIL_BUF_HOOK_FUNCTION_PTR HookHandlerPtr, //in
void * UserDataPtr //in-out
)

Description

This function allows you to attach or detach a user-defined function to a specified buffer or container event (for example, a modification to the buffer's contents). Once a hook-handler function is defined and hooked to an event, it is automatically called when the event occurs.

You can hook more than one function to an event by making separate calls to MbufHookFunction for each function that you want to hook. Aurora Imaging Library automatically chains and keeps an internal list of all these hooked functions. When a function is hooked, this new function is added to the end of the list. When the event happens, all user-defined functions in the list will be executed in the same order that they were hooked to the event. You can also remove any function from the list; in this case, Aurora Imaging Library preserves the order of the remaining functions in the list.

Parameters

ContainerOrBufId (in, AIL_ID)

Specifies the identifier of the buffer or container.

HookType (in, AIL_INT)

Specifies the buffer event to which to hook the function. This parameter can be set to one of the following values:

For specifying the buffer event

ValueDescription
M_FEATURE_CHANGEHooks the hook-handler function to the event that occurs when the value of a GenICam feature changes.

To enable an event to occur when the value of a specific feature changes, use MbufControlFeature with M_FEATURE_CHANGE_HOOK set to M_ENABLE. Repeat for each feature that you want to enable a feature change event. To enable an event to occur when the value of any feature changes, use M_FEATURE_CHANGE + M_ALL. This setting is only available for hooking to an image buffer.

To retrieve the name of the feature that caused the event, use MbufGetHookInfo with M_GC_FEATURE_CHANGE_NAME. | | M_LAYOUT_MODIFIED | Calls the hook-handler function when at least 1 component of a container has been added or removed. The hook-handler function is called once at the end of a function regardless of the number of changes. | | M_MODIFIED_BUFFER | Calls the hook-handler function at the end of any Aurora Imaging Library function that modifies the specified buffer or container.

Note: For a container, this event will occur any time the container is used a destination for an Aurora Imaging Library function (unless none of the container's components is modified), any time a component is added to or removed from the container, as well as any time one of the container's components is modified directly using its Aurora Imaging Library identifier. The hook-handler function will only be called once per call to an Aurora Imaging Library function, unless M_ON_COMPONENTis specified. |

For hooking the function to changes in components

ValueDescription
M_ON_COMPONENTSpecifies to hook to changes in each component of the container individually, instead of to the container as a whole. When a component of the container changes, the hook function will be called as though it were hooked to that component. UsingMbufGetHookInfowith M_BUFFER_ID within the hook-handler function will return the buffer identifier of the component.

For

ValueDescription
M_ALLSpecifies to hook the specifies function to all feature change events.

For specifying that the function should be unhooked

ValueDescription
M_UNHOOKUnhooks the specified function if hooked to the specified event. When you use M_UNHOOK, you must provide the same values for all the parameters as when you originally hooked the function.

HookHandlerPtr (in, AIL_BUF_HOOK_FUNCTION_PTR)

Specifies the address of the function that should be called when the specified event occurs. The hook-handler function must be declared as follows:

UserDataPtr *(in-out, void)

Specifies the address of the user data that you want to make available to the hook-handler function. This address is passed to the hook-handler function, through its UserDataPtr parameter, when the specified event occurs. Set this parameter to M_NULL if not used.

Copyright © 2026 Zebra Technologies.