Currently when one wishes to trace events, one would restart NVDA with debug logging enabled. At the moment all sorts of UIA events from all apps will be tracked, but there might be situations where one may wish to troubleshoot event tracing with just one or two events and/or inside one or two apps.
Thus introduce a series of command-line switches unique to this add-on that will allow users and developers to limit event tracing to an app (given its executable) and events. Also, if any of these new switches are given, enable event tracing in log levels other than debug mode so people can report event tracing issues without being bogged down by all sorts of debug output.
josephsl
commented
3 years ago
Hi,
Currently when one wishes to trace events, one would restart NVDA with debug logging enabled. At the moment all sorts of UIA events from all apps will be tracked, but there might be situations where one may wish to troubleshoot event tracing with just one or two events and/or inside one or two apps.
Thus introduce a series of command-line switches unique to this add-on that will allow users and developers to limit event tracing to an app (given its executable) and events. Also, if any of these new switches are given, enable event tracing in log levels other than debug mode so people can report event tracing issues without being bogged down by all sorts of debug output.
Thanks.