Quote from: Wilma on January 10, 2014, 12:45:28 PM

Hello Ighor,

Thank you for your reply.

I wish we could have more open discussion about the rules and because it seems the exchange is not very fertile I am opening a bit of my experiences of testing and playing with them. Hopefully I am able to get some comments and hints how to use the QT Trader more effectively and one point to be able to make money instead of loosing it.

Few questions:
1. What do you need to do if you want to trade USD-BITCOIN and USD-LITECOIN at the same time? Is it enough to have one API key to USD-BTC, another API key to use with USD-LTC, and then just launch two different QT Trader programs with different user accounts at your PC?

You need two pairs of API keys for now. And make requests interval twice larger. So you will be able to run two instancess of program without issues.
Also I think I'll make improvements on BTC-e and multi currency trading will works soon.

Quote from: Wilma on January 10, 2014, 12:45:28 PM

2. Would be great to have possibility to set rules with % (I know it is coming) and also possibility to execute them x many times on top of the sequential and concurrent modes.

I'm currently working on it.

Quote from: Wilma on January 10, 2014, 12:45:28 PM

3. This might be totally stupid question but why there is no possibility to trade between different exchanges for example between BTC-E and Mt.G?

I have planted multi exchange trading support to Qt Open Trader.

Quote from: Wilma on January 10, 2014, 12:45:28 PM

For my surprise trade "Group 2" was made like it should, but the Qt Trader did not show it to me when the program was running.

Does anyone else have the same problem and why this happens?

What did I set up wrong since the rule "Group 2" sold all my BTC but "Group 3" did not protect my balance?

This is a bug and I have fixed it. Update will be available soon.

Quote from: Squeaker on January 10, 2014, 03:17:52 PM

From looking over my fork of the code, when there are orders waiting to be submitted, those get priority over other API calls, so you could continue to send trade orders in while the balances and prices haven't been updated. (this seemed more of an issue on polled exchanges like BTCe. I didn't notice it happening on MtGox, which I am assuming is because of MtGox's streaming socket taking a more active role in keeping API clients current. I don't do much trading on MtGox, however, with only a balance of 0.4 BTC there, for testing purposes, so perhaps that has something to do with it too.)

I had to make some changes to disable the USD/BTC price boxes whenever a trade was sent in, and all rules would fail (except for enable/disable rules and cancel order actions) until the client received an updated balance from the exchange (even if the actual balance hadn't changed yet, the exchange at least confirmed that the numbers were still good)

I also had to implement my own delay between executing a trading rule, allowing the client time to update the exchange info, as the built in safe-mode delay I could never get to function properly.

Unfortunately, these changes would not be compatable with the existing code now as I have changed too much code to make merging the patch possible, but this should give ideas of where the problem lies, and a possible solution to deal with it, for someone else who is actively contributing to the main branch.

=squeak=

I have already made rules fixes. And now rules executing correctly. I'll publish update soon.

You can tell me about your implementation of delay, and why safe-mode delay not works for you?