New TC user here, been using it intensively for about 2 weeks and it's a great program! In fact, I'm seriously considering replacing the miriad data capture scripts I have developed/adapted over the years and start using TC exclusively.
In the first place I want to thank @HKJ for gifting this excellent software to us all, and for the support he keeps providing us both here in EEVBlog (which I joined just because of this thread) and on
BLF (which is where I initially became aware of it).
Its major deficiency for me is it not being opensource; of course I respect @HKJ decision in keeping the source closed, but at least for me it would be much better if it was open-source, as then I would be able to look at the code to understand what it does (it would have saved a lot of back-and-forth PMs between me and @HKJ when I encountered difficulties connecting to virtual serial ports in my system -- @HKJ kindly helped me through them and the TC documentation is not bad, but IME there's no substitute for the "Use the Source, Luke" method when dealing with such details).
Also, it would allow me to contribute code to implement the other things I see as minor deficiencies; so here I leave them as suggestions:
1) AFAICS there's no way to clear the data that has already been captured (ie, the data showing up in the "Table" tab/window) except implicitly by initiating a new "Log", or exiting and reentering the program; an explicit way of doing that (eg, a "Clear Data" or similar button in the "Table" and/or "Command" tabs/windows) would IMO be a useful addition.
2) Also, when one starts a new log, or exits the program, without saving the data already captured, the data is lost without any warning; I would like to suggest that a warning dialog window, eg "Current data not saved, proceed?" with two buttons eg "OK" to proceed and lose the data, and a "Cancel" button to abort the exit or start log operations, and perhaps a 3rd button "Save" to be able to save the data directly from that dialog, could be shown whenever that is about to happen. This would have helped me avoid a couple of data losses (and repeated captures) I went through here (I know, my fault for not double-checking I had the data saved before exiting or starting a new log, but the one who never made that kind of mistake may throw the first stone

)
Just my $0.02. And thank you again @HKJ! 👍👍👍