"be consistent" | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Okay. The code I posted will miss intermediate values if the incoming values arrive faster than the screen update checks for them. If your application need to reflect every change, and if it can update the screen as fast or faster than the input arrives, that would not occur. If you cannot update the screen as fast as the input arrives, then eventually you will have to either combine multiple inputs into a single update, or discard intermediates. Either way, to ensure than your update thread sees all the inputs, it must either run faster than the inputs arrive, or they must be queued Here is a queued solution.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
In reply to Re^3: Perl/Tk App and Interprocess Communication
by BrowserUk
|
|