You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
The numbers under your avatar don't belong to you, so you have no power over them (you can't change them at will).
I don't want to change it myself, please :)
Well, if you can't change it by 1000, at least multiply it by 100.
I don't want to change it myself, please :)
Well, if you can't multiply it by 1000, at least multiply it by 100.
The numbers under your avatar do not belong to you, so you have no control over them (you cannot change them at will).
Added.
Forget about orders before transaction with type TRADE_TRANSACTION_DEAL_ADD. Why "forget it"? Because it's the wrong thing to do.
Forget about transactions, I'll tell you in confidence that you can find out about transactions from history,
when the historical transaction came in. There is no order, so you can see what the order has "made".
With this simple function:
Forget about transactions, I'll tell you in confidence that you can find out about transactions from history,
when the historical transaction arrived.
With this simple function:
You are inattentive:
...
Forget about orders until a transaction of type TRADE_TRANSACTION_DEAL_ADD. Why "forget"? Because this is WRONG.
Then you can remember about the warrants.
You are inattentive:
Then you can remember about the warrants.
Thanks, I'll try not to forget :)
So what about the x100?
Added:
Just here's the trouble:
The Transaction comes first, how do I know if it's the first?
Or vice versa Transaction comes first.
Thanks, I'll try not to forget :)
So what about the x 100?
I already did:
Forum on trading, automated trading systems and trading strategy testing
"Floating PositionSelect() error
Karputov Vladimir, 2016.08.15 17:44
Not allowed. Not allowed. Impossible....
Added:
Just here's the trouble:
Hist. transaction comes first, but how do I know it's first?
Or vice versa The transaction comes first.
I need to think about it. Please clarify, is it when an order with a volume of more than 1 is triggered?
If everything worked asMQ Alexandersaid, then
there wouldn't have been any problems.
As it is, it's impossible to tell... :(
Because the transaction may already be in the history before the Deals done: 1.0.
And according to Aleksander's words, it would work like this ( and would be right! ):
When historical transaction arrives:
Volume initial - Volume current = Deals done - Transaction already arrived
Don't put a flag and deal with positions and orders!
--------------------------------
Volume initial - Volume current != Deals done - Deals transaction is next
You should set the flag, wait for the Deals transaction and use the flag to deal with positions and orders!
That is all!