Possible design for stateless notifiers

[infinitenothing]

Inspired by these two threads:

http://lavag.org/topic/18657-notifiers-not-working-when-use-consecutive-create-notifier-vis-without-delay/

http://lavag.org/topic/4028-notifier-signals-missed/

 

I was wondering if I could create my own notifier that could switch between references without the history management. Here's what I came up with. I'm not expecting this to be very fast. I thought it was an interesting use case for occurrences.

 

Test Case:

Obtain Notifier

Wait on notification

I probably need a mechanism to check and retry if the "Latest Message Is Valid" flag is false after the "Wait on occurrence".

 

Send Notification

Edited December 2, 2014 by infinitenothing

[drjdpowell]

I don’t think you an avoid a history recorded somewhere.  Your solution above won’t get notifications that occur between calls to “Wait on Notificationâ€.  Though if you were to keep a history of listeners in the Notifier structure (in contrast to the current LabVIEW Notifier that keeps a history of Notifiers in the Wait node), then this might be better, as the list of Wait nodes should be finite, in contrast to the potentially limitless number of Notifiers.

[infinitenothing]

You're not supposed to get notifications that occur between WON if you set the ignore flag to true are you?

[drjdpowell]

Oh, I missed that case structure (I can’t read VI snipits on my machine).   So you are building a Listener history. 

[infinitenothing]

It's building a listener list (no time stamp) but it's not stored in the internal state of the WFN. It's limited to how many nodes you have (like you said).