[Archive!] Any rookie question, so as not to clutter up the forum. Professionals, don't pass it by. Couldn't go anywhere without you - 2. - page 511
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
Hello !
Looking for a script, topic created here https://forum.mql4.com/ru/42138 advised to contact here for help.
Thanks in advance!
You have been advised - look here, dig the codebase - don't forget to share your results.
You were told to look here, dig the codebase - don't forget to share your results.
I wrote that I couldn't find anything there :(
https://forum.mql4.com/ru/5006/
https://forum.mql4.com/ru/5006/
Also not the same, because to open a position on limit or market you need to use different scripts + you have to find the instrument itself and open its window + there is no partial closing of positions.
there's something wrong here!
There's a mandatory zeroing before the comparison.Of course it's not:
I've already told you the address where it will be done exactly the way you want it done, I won't repeat it.
Yeah, yeah, I hear you... but before I give you my money I'd like to make sure the script I need isn't freely available
Good afternoon.
There are 4 orders, 2 sells and 2 buys. Seals are created, figuratively speaking, when the price goes up and buy when it goes down. The sells are deleted when a buy is created and vice versa. When a ticket is created, the 1st sell or buy is stored in the variable pos. All 4 have the same comment - "Aelit". So, there is a code:
Theorder is selected normally by the ticket, but very often the comment comparison fails. For interest, I made else Alert(OrderComment()); and the log showed "Alert: Aelit[sl]". What is [sl]? Is it because all orders have the same comment? Then why was the same [sl] when I made a comment that didn't match the others for the test? If you remove the comment check, there is a ticket error in the log for OrderModify. At first I thought the condition was reached before any order was created, but no, at that time the order is already there, and the ticket is the same in case of condition triggering and not triggering. How do I understand it?