Search the Community

I’m working on a project using the Actor Framework to remotely control an oscilloscope. The actor responsible for the oscilloscope overrides the Actor Core to run a loop that acquires data, which is then sent to the root actor for processing. The issue is that when stopping the root actor, the oscilloscope actor throws an error when trying to send the data (which is expected, since the root actor no longer exists). However, the problem is that when executing Stop Core—where the acquisition and UI loops are stopped—for some reason error 1 is generated and the actor does not shut down properly. On the other hand, when sending the Stop message, it does stop correctly. Any ideas? Thanks in advance! Generic Oscilloscope.zip

Debugging an application of mine, I ran into a very possible occurrence of https://lavag.org/topic/9986-out-of-order-events-is-not-a-bug-sort-of/ . Now, I have reasons to suspect that, due to some race, while in the IDE I have a positive timestamp difference between one certain dynamic and another user event, in the compiled application the two can be nearly simultaneous. Enough for treating the race in the first place, but academically wondering: in the IDE I can help myself out with the Event Inspector; can anyone suggest a way to filter and display information from the event queues in the apps? Looking at the GUI of the Event Inspector, that looks like one of these many tools written in G, modulo using password protected blocks, I haven't been diligent enough to search for its whereabouts yet. LV2014.1. Otherwise, for the present case, I suppose that just sequencing the event generating blocks together with a Clock Tick and displaying the results may do, for the debugging I need. TIA, Enrico