If one TurKit run starts before another finishes, bad things happen. Mostly
this is OK except for making C# deal with lots of extra messages. The bad
behavior comes about when this happens:
- One paragraph has finished find-fix-verify
- Another paragraph is still working on some stage
TurKit runs and sends the complete data for the first paragraph. It then shuts
down. C# ticks off that paragraph as complete. TurKit runs again and sends the
same complete data. C# marks off another paragraph as complete. It thinks both
paragraphs are now complete, even though only one is.
Resulting behavior: Shortn shows two copies of the same paragraph.
Possible fixes:
1) put status messages in once() clauses so that they don't get sent so often.
This is probably a good long-term solution. Allow C# to call TurKit with
another flag to request the messages get sent again outside a once() clause,
for example when replaying history on startup.
2) fix the message receiver code so it is more particular about not finishing
when only one paragraph is done
#2 is faster; #1 is right.
Original issue reported on code.google.com by esperte...@gmail.com on 8 Sep 2010 at 2:47
Original issue reported on code.google.com by
esperte...@gmail.comon 8 Sep 2010 at 2:47