Strange behavior with ExtraTaskSettings.TaskDeviceName
Posted: 14 Jul 2018, 02:47
I've noticed an unusual behavior of the global ExtraTaskSettings.TaskDeviceName var. I expect it to match the name of the Plugin that is in scope. It normally is, except for the PLUGIN_WRITE state.
When a write action is being process the ExtraTaskSettings.TaskDeviceName is unpredictable. It is always the name of a define device, but not always the correct one. What I mean is that when a PLUGIN_WRITE event is being processed by Device A, the ExtraTaskSettings.TaskDeviceName within the WRITE case state is sometimes the name of Device B or Device C, and so on.
Is this normal behavior? If it is, how can I get the correct name of the plugin while in its PLUGIN_WRITE state?
- Thomas
When a write action is being process the ExtraTaskSettings.TaskDeviceName is unpredictable. It is always the name of a define device, but not always the correct one. What I mean is that when a PLUGIN_WRITE event is being processed by Device A, the ExtraTaskSettings.TaskDeviceName within the WRITE case state is sometimes the name of Device B or Device C, and so on.
Is this normal behavior? If it is, how can I get the correct name of the plugin while in its PLUGIN_WRITE state?
- Thomas