Extensive changes in CTtext, most of them "under the hood". The GUI and CTwriter now execute in asynchronous threads; this is important, for instance, when sending data via FTP so as to not make GUI behavior choppy. CTtext's framework is now similar to that of CTscreencap. In both programs, data to send to CT is put on a queue; an instance of WriteTask (which executes in its own thread) takes objects off the queue and sends them to CT.
Inline documentation in the CTtext.java header describes program flow.
The only significant GUI change is that there are separate menu items to start data flow to CT and to stop CT. This seems better than the previous method, where the user had to bring up the Settings dialog and clicks OK before CT data flow started.
Extensive changes in CTtext, most of them "under the hood". The GUI and CTwriter now execute in asynchronous threads; this is important, for instance, when sending data via FTP so as to not make GUI behavior choppy. CTtext's framework is now similar to that of CTscreencap. In both programs, data to send to CT is put on a queue; an instance of WriteTask (which executes in its own thread) takes objects off the queue and sends them to CT.
Inline documentation in the CTtext.java header describes program flow.
The only significant GUI change is that there are separate menu items to start data flow to CT and to stop CT. This seems better than the previous method, where the user had to bring up the Settings dialog and clicks OK before CT data flow started.