Here is a list for issues and improvements that could be done with cat:
1. delete older logs during the running of the cat, but not only during start-up.
Many users use VPS, VM, dedicated machines with limited resources. With long time run CAT at many markets use a lot of disk space, which could to cause a problem. Making thread inside application that will just periodically run cleaning routines will do the work.
2. UI dialogs for Save/Load market/order is not very well designed.
It would be good in dialogs for load and save will have the caption with exact action that was selected (not a 'Select', but for example 'Save Market Orders'). If you misclick at UI, you could verify with dialog name this.
Second it's a default filters for save/load files. Since we work with xml files I suppose need to use it as default filter for file selection. And as a option *.* if user use other extension.
3. Load market/order didn't load correctly values to the pool. I.e. if you run cat with some value in pool, save market/order, restart cat, load market/order pool value will be 0. If users algo is based on limiting ping order it is effectively stop algo from working at all.
3. Orders & Trades -> Ping Trade table usually come with error during editing values inside there. For example, you have 2 orders in Ping Trade, and want to edit both of them. Usually, work only first one, the second one showed error with null pointer exception. Editing pings orders and pongs orders could cause to same errors too, but it's a mostly when you edit order in the time when it fired in market. It seems to me, logic of working with editings of orders is not safely designed.
4. UI part with presets work. When you load market/orders from the file, 'presets' combo box show 'Default Dynamic' instead of 'Current Running'. it confuses.
5. Columns in the spreadsheets of the gains are not aligned to the width of data inside each column.
For example column "Start Trade" will have only 4 chars, but it have width same to the Cumulative Gain, which could be millions of value or Timestamp that is not fit well to the default width of column
thank you so much for all of these suggentions.
I can tell you that :
1 - I'm working on it actually to split files when size will reach X (where X is an user parameters).
I will try to add an option like "Delete older files in log files folder if total size is > X)
This will cause a problem : if some error occurs i won't be able to analyze market log, BUT this is a choise from users side.
2 - Dialog about save/load will be refactored with another improvements on XML Data save (i will save buy/sell pool values and trades that actually are not saved)
3 - I need to check this but i think null pointer exception could be fixed in 5.0 version, but if you are able to get the same error with 5.0 pls pm me about that.
4 - Agree
5 - I think i have a code to "optmize" column size. Need to check