The idea is pretty simple. When I probe an enqueue, I don't want to just see what is being placed on the queue, I want to see where that value is being de-queued.
I have a large legacy project which has a lot of inter-process communication. Queues are used for a lot of this. When I look at code where an element is enqueued, my debugging or code review comes to a screeching halt because I don't know where the data is being dequeued. The project does not use named queues.
This is mostly not a matter of a GUI process communicating with a command and control process in the same VI. It is more of a matter of dynamically loaded drivers passing data back to one of several other processes as conditions change.
I think that I can figure this out with the Trace Toolkit, but it would be cooler if I could just put down a probe and have it tell me where the Dequeue is. (If there were some kind of design time tool that I could use to map the Queue references this would be the coolest of all.)
I know adding a picture helps get the idea across, so here is a fast mock up. Note the red circle in the lower right.