ENUM_ORD_REAL_STATE rl_state = CheckOrderState( ticket );
//--- switch( rl_state )
{
case ORD_NOT_SPECIFIED:
case ORD_NONE_CANCELED:
case ORD_NONE_PARTIAL_CANCELED:
case ORD_NONE_PARTIAL:
case ORD_NONE_EXPIRED:
case ORD_NONE_FILLED:
case ORD_NONE_REJECTED: Canceled();
break;
case ORD_BUSY: return;
break;
case ORD_EXIST:
case ORD_EXIST_PARTIAL: Remove();
break;
}
Right, typo :)
Thanks, corrected it...
I often get confused myself ) Uncomfortable and incorrect order handling functions.
I often get confused myself ) inconvenient and incorrect order handling functions.
there is still one place left to go:
It didn't take long for MQ Alexander's "joy" to be explained!
I check before deleting the order:
Result:
Maybe you're checking it wrong. The code is broken, there are a lot of gaskets.
It's so screwed up that you won't know exactly what state wasORDER_STATE_PARTIAL or ORDER_STATE_PLACED to understand anything further.
How can one live with such messages? It looks like there is an attempt to delete the order and the message "The order has not been sent!
Maybe you're checking it wrong. The code is broken, there are a lot of gaskets.
It's so screwed up that you won't know exactly what state wasORDER_STATE_PARTIAL or ORDER_STATE_PLACED to understand anything further.
How can one live with such messages? It looks like there is an attempt to delete the order and the message "The order has not been sent!
https://www.mql5.com/ru/forum/58012/page2#comment_2017705
It still does not shed any light on what wasORDER_STATE_PARTIAL or ORDER_STATE_PLACED
Here:
Here:
What is it?