Setting Promptschedule0prompttext or Promptschedule1prompttext from an Execute DAT (onFrameStart) or via run() triggers 'TouchDesigner objects cannot be referenced from separate threads' warning dialog. The warning blocks the UI and makes the plugin unusable for dynamic prompt control.
Steps to reproduce:
Create Execute DAT with onFrameStart
Set op('Daydream').par.Promptschedule0prompttext from script
Thread conflict dialog appears and blocks interface
Even using run() with delayFrames, the plugin's internal param change handler reads TD objects from its background thread.
v0.2.3, TouchDesigner 2025.32460, macOS Tahoe 26.3.1, MacBook Pro M3
Setting Promptschedule0prompttext or Promptschedule1prompttext from an Execute DAT (onFrameStart) or via run() triggers 'TouchDesigner objects cannot be referenced from separate threads' warning dialog. The warning blocks the UI and makes the plugin unusable for dynamic prompt control.
Steps to reproduce:
Create Execute DAT with onFrameStart
Set op('Daydream').par.Promptschedule0prompttext from script
Thread conflict dialog appears and blocks interface
Even using run() with delayFrames, the plugin's internal param change handler reads TD objects from its background thread.
v0.2.3, TouchDesigner 2025.32460, macOS Tahoe 26.3.1, MacBook Pro M3