07-29-2019 09:24 AM
Thanks for bringing this up! I've just filed a Service Request about this "anomaly", referencing this Forum Post, and expect that this will get "escalated" to the team responsible for Care and Feeding of Channel Wires. I will update this Forum post as I learn more.
Bob "Channel Wire Enthusiast" Schor
07-29-2019 09:28 AM
Just found that you can create a One Element Channel reader, then right-click Replace-->Channel Endpoint and pick One Element Channel With Abort. So it's only when creating it without a channel reader in place, if that helps localize the bug.
@Bob_Schor wrote:
Thanks for bringing this up! I've just filed a Service Request about this "anomaly", referencing this Forum Post, and expect that this will get "escalated" to the team responsible for Care and Feeding of Channel Wires. I will update this Forum post as I learn more.
Bob "Channel Wire Enthusiast" Schor
07-30-2019 12:54 PM
I have heard (indirectly) from LabVIEW R&D that they have verified the behavior of the One Element Stream with Abort Channel that has been reported here, both the problem creating a Reader (with Abort) and the "work-around". A CAR (Corrective Action Record? ... Report?) will be filed, and "Something Might Be Done". This is usually accomplished by being included in a Patch Release, an SP1 Release, or a subsequent Version of LabVIEW. If/when I hear more, I'll post again.
Thanks, @cous, for finding this "feature" (there are no bugs, of course) and posting it here!
Bob Schor
07-30-2019 01:00 PM
Thanks @Bob_Schor for pushing to get the CAR filed for this Fingers crossed that it makes the cut for implementation in the next release...