Closed francois-normandin closed 6 years ago
I'm closing this feature and marking it as "Will not implement". I'm unsure of the value of this feature I proposed. One factor to consider is the blocking of root thread when launching asynchronously. This feature would be impacted by dialog boxes and the likes, creating uncertainty in timing and be very difficult to debug.
An asynchronous wrapper call on the dynamically dispatched callbacks would ensure that no race conditions or mishandled errors can block the workflow.
Callback VIs (onStart, onStop, onCreated, etc.) can make recursive calls to dependencies, which might contain blocking conditions that cannot be terminated gracefully. If the callback is wrapped in an async method waiting for execution to complete, framework can enforce thread termination on error. (This mechanism should work for both byVal and byRef classes)