11-29-2018 07:48 AM - edited 11-29-2018 11:00 PM
In this discussion, drjdpowell mentioned the asynchronous calls in the Actor Framework as an example. When I was looking for all instances of Start Asynchronous Call, I noticed that they are different from each other - Launch Actor Core mentions a workaround for RT and uses non-strict references, while Time-Delayed Send Message does not.
Is this just a change that didn't propagate to all calls, or are there some circumstances where you would intentionally want strict references wired in the Time-Delayed Send Message way?
Screenshots from LabVIEW 2018f1
Solved! Go to Solution.
11-18-2019 05:54 PM
Someone pointed that out to me recently. I've made the same fix in LV 2020 for Time-Delayed Message.
11-18-2019 05:55 PM
I wish I could get the RT bug fixed, but it doesn't affect many VIs, and I haven't been able to get the team to make it a priority since the workaround exists.
11-19-2019 07:19 AM
What is the RT bug?
11-19-2019 10:28 AM
@drjdpowell wrote:
What is the RT bug?
Some sort of root loop priority inversion.
11-19-2019 11:02 AM
I suspect this is the same issue as CAR 678300.
https://labviewcoder.com/2016/07/06/quick-tip-asynchronously-launching-vis-the-right-way/