Trace Components Event Logger v1.0.1

Q-SYS plugin Trace Components Event Logger

Usage:

1. Allow script access to the target component.
2. It is recommended to use QDS 9.5 or later, which allows script access to UCI control from the touch panel.
3. When you emulate or start the system, the plugin detects the components, and you select the target control.
4. When Trace is Active, it is running.

The behavior of the target module is written to the local log or the Core event log with or without a timestamp. If the local log exceeds 400KB, it will sequentially back up logs to the ExportLog folder in Core. Writing to the Core event log allows for double-checking during malfunctions.

Metadata changes cannot be traced. These are:

• .IsInvisible, .IsDisabled, .IsIndeterminate, .Color, .Choices, .Legend

However, EventHandlers for changing the above can be traced.

Additionally, please do not trace the event logger, event log, or the plugin itself. This can cause the event handler to loop and not stop.

*Note and Caution-------------------------------------------------------------

As you know, use this plugin at your own risk.

Trace only the components you need. I do not know what will happen if you run it on all components.

By adjusting chunk size and interval time, It managed to process table sizes up to 6557 in tests.

Too many script-accessible components will slow things down.

RealTime Update is highly loaded.

You should usually turn it off only when checking

In the test, writing one log.txt requires 396KB, and there are 4803 lines of remaining logs.

It is recommended to use QDS 9.5 or later