09-26-2006 11:18 AM
09-26-2006 12:18 PM
09-26-2006 01:59 PM
Can you post a simple test VI that shows this behavior? It seems likely that the Reader loop is thread-starving the writer loop since both were initially set to polling.
09-26-2006 02:34 PM
I think you are correct in your logic. I've attached my quickly developed test vi.
If the timeout on the read loop is put to another number other than -1 say 10000, then the program is straved for that amount of time if when it enters the read no item is avaliable.
In order to view this behavior you will have to set the r/w mode to (polling, polling).
09-27-2006 10:28 AM