MaaCtrlOptionRecording indicates that all screenshots and actions should be dumped.

MaaCtrlOptionScreenshotTargetLongSide specifies that only the long side can be set, and the short side is automatically scaled according to the aspect ratio.

MaaCtrlOptionScreenshotTargetShortSide specifies that only the short side can be set, and the long side is automatically scaled according to the aspect ratio.

MaaCtrlOptionScreenshotUseRawSize specifies that the screenshot uses the raw size without scaling.

MaaGlobalOption_DebugMode Whether to debug value: bool, eg: true; val_size: sizeof(bool).

MaaGlobalOption_LogDir Log dir value: string, eg: "C:\\Users\\Administrator\\Desktop\\log"; val_size: string length.

MaaGlobalOption_Recording Dump all screenshots and actions Recording will evaluate to true if any of this or MaaCtrlOptionEnum::MaaCtrlOption_Recording is true.

MaaGlobalOption_SaveDraw Whether to save draw value: bool, eg: true; val_size: sizeof(bool).

MaaGlobalOption_ShowHitDraw Whether to show hit draw value: bool, eg: true; val_size: sizeof(bool).

MaaGlobalOption_StdoutLevel The level of log output to stdout value: MaaLoggingLevel, val_size: sizeof(MaaLoggingLevel) default value is MaaLoggingLevel_Error.

I don't recommend setting up MaaResOption_InferenceDevice in this case, because you don't know which EP will be used on different user devices.

MaaResOption_InferenceDevice will be used to set coreml_flag, Reference to https://github.com/microsoft/onnxruntime/blob/main/include/onnxruntime/core/providers/coreml/coreml_provider_factory.h But you need to pay attention to the onnxruntime version we use, the latest flag may not be supported.

MaaResOption_InferenceDevice will not work.

MaaResOption_InferenceDevice will be used to set NVIDIA GPU ID TODO!.

MaaResOption_InferenceDevice will be used to set adapter id, It's from Win32 API `EnumAdapters1`.

Use the specified inference device.

Use the specified inference execution provider Please set this option before loading the model.

for adb controller, contact means finger id (0 for first finger, 1 for second finger, etc) for win32 controller, contact means mouse button id (0 for left, 1 for right, 2 for middle).

for adb controller, contact means finger id (0 for first finger, 1 for second finger, etc) for win32 controller, contact means mouse button id (0 for left, 1 for right, 2 for middle).

MaaAdbInputMethod Use bitwise OR to set the method you need, MaaFramework will select the available ones according to priority.

MaaAdbScreencapMethod Use bitwise OR to set the method you need, MaaFramework will test their speed and use the fastest one.

DbgControllerType No bitwise OR, just set it.

MaaWin32InputMethod No bitwise OR, just set it.

MaaWin32ScreencapMethod No bitwise OR, just set it.