[...]You don't have to, nor should you, post the entire code in question.
Does this make more sense? I can provide additional information if
needed. I would prefer to steer clear of posting the actual code on a
public group board, but would be willing to have a personal
discussion.
Simply construct a concise-but-complete code sample that demonstrates the
issue. Leave out everything that isn't directly related to the issue
itself.
A suitably abridged code sample will necessarily not contain any
proprietary information and so would be perfectly fine to post publicly.
As Anthony said, if you have a method named NewData() that has in it a
call to another method C() that is unconditionally executed, then once
NewData() returns to the caller, you are _guaranteed_ that the method C()
has been called.
Without an actual code example, it's impossible to truly understand your
question. It seems likely to me that if for some reason your UI can't
keep up with the data stream, then either you'll need to make the UI code
more efficient, or you'll need to include some explicit throttling to
ensure that you don't actually update the UI with every single event on
the data stream.
But without seeing the actual code, there's no practical way to provide
advice as to how to do that.
Pete
