Maximum length of a symbol name on FOREX - page 7

New comment
 
prostotrader:

I have never needed to find out which EA has traded how much.

Each EA has its own percentage of risk and profit - that's what interests me.

It's you FOREX people who are always concerned about some magical calculations.

99% are looking for the "Grail", which does NOT and CANNOT exist, and 1% are quite newbies, who look into the mouths of experienced loss-mongers.

The explanation, most likely, is that "trading" on FORTS is "not for their own" and "not for pennies"?

 
aleger:

The explanation, most likely, is that "trading" on FORTS is "not on their own"?

Why not with your own money? It is with my own money.

But, of course, in order to confidently trade on FORTS in the beginning you need at least 250,000 - 300,000 rubles.

And do not take the word TRADING, as used in the FORTS, in quotes, quotes should be put for FOREX.

 
prostotrader:

Why not with your own money? With your own hard-earned money.

But, of course, to confidently trade on the FORTS in the beginning, you need at least 250,000 - 300,000 rubles.

And there is no need to take the word TRADING, as used in the FORTS, in quotes, you have to put quotes for FOREX.

Personally, I consider Forex solely as "watching currency rates change".

 
prostotrader:

I have never needed to find out which EA has traded how much.

Each EA has its own percentage of risk and profit - that's what interests me.

It's you FOREX people who are always concerned about some magical calculations.

The 99% are looking for the "Grail", which does not and CANNOT exist, and the 1% are very newbies, who look into the mouths of experienced "sinkers".

There is no difference between forexers, stockbrokers and cryptophiles. Everywhere there are bets on rate changes.

prostotrader:

For FORTS, the two low bytes allow (65535) to assign each new order its own magik, searching for an order is quick and easy and

easy to understand.

You can also free up two bytes to suit your needs in the CRC solution. I don't understand why each order has its own magik.

 
fxsaber:

There is no difference between forex traders, stockbrokers and cryptophiles. Betting on exchange rate changes is everywhere.

Well, well...

You can also free up two bytes for your own needs in the CRC solution. I don't understand why each order has its own magik.

I use OrderSendAsync() and TM5 very often makes huge delays, by requester ID it's impossible to track

order and you can do it with a magik

 
prostotrader:

I use OrderSendAsync(), and TM5 very often makes huge delays, you can't track by requisition ID

of the order, but you can do it with a magik

So it turns out that you somewhat hammer the work of OnTradeTransaction and see if the order with the right magician is present among the living/dead?

 
fxsaber:

So you are somewhat blocking OnTradeTransaction and see if there is an order with the right wizard among the living/dead ones?

No, I do not, but if OnTradeTransaction is not triggered within a second, the search function of the order by magician is activated.

I memorize the times and then I compare them

//+------------------------------------------------------------------+
//| Place order                                                      |
//+------------------------------------------------------------------+
void COrder::Place(const double price, const double volume, const bool buy_sell)
{
  MqlTradeRequest request = {0};
  MqlTradeResult  result  = {0};
  ticket = 0;
  req_id = 0;
  mem_magic = magic_storage + 1;
  check_count = 0;
  if(magic_storage >= (magic_number + 65530)) mem_magic = magic_number;
//--- Fill structure
  request.action = TRADE_ACTION_PENDING;
  request.magic  = mem_magic;
  request.symbol = a_symbol;
  request.volume = volume;
  request.price  = price;
  if(buy_sell)
  {
    request.type = ORDER_TYPE_BUY_LIMIT;
  }
  else
  {
    request.type = ORDER_TYPE_SELL_LIMIT;
  } 
  request.comment = "Отложенный ордер...";      
  request.type_filling = ORDER_FILLING_RETURN;
  request.type_time = ORDER_TIME_DAY;
//--- Send order
  if(OrderSendAsync(request, result) == true)
  {
    if((result.retcode == TRADE_RETCODE_PLACED) || (result.retcode == TRADE_RETCODE_DONE)) 
    {
      req_id = result.request_id;
      magic_storage = mem_magic;
      state = ORD_DO_SET;
      mem_time = GetMicrosecondCount();
      mem_start_time = TimeCurrent();
      SetTransCount();
    }
    else
    {
      mem_magic = 0;
      mem_time = 0;
      mem_start_time = 0;
      CheckError(result.retcode, "Place: Ордер не установлен! Причина: ", order_status, ticket);
    }
  }
  else
  {
    mem_magic = 0;
    mem_time = 0;
    mem_start_time = 0;
    CheckError(result.retcode, "Place: Ордер не отослан! Причина: ", order_status, ticket);
  }
}
 
prostotrader:

No, not scoring, just if OnTradeTransaction is not triggered within a second, that the order search function by magik is triggered.

In fact, it is scoring. As it is possible to not wait for a trace to be triggered. The only thing without an OnTradeTransaction is if the order is rejected. For example, if there is not enough money.


It turns out that we made a hundred Async-transactions filling the array (list) with appropriate mages and requesters. As soon as OnTradeTransaction received the response on the quest, we removed the element from the list. As soon as we saw the highlighting of a majic from the list among the living/dead, we removed the entry. That's how control is achieved more or less. Have you got it right?


You can still use other fields - SL/TP, Comment - instead of magic.

 
fxsaber:

In fact, it's a hammering. Since it is possible to not wait for the order to be tracked. The only non-alternative onTradeTransaction is if the order is rejected. For example, if there is not enough money.

If you like it that way, let it be "scoring", but after the first check, we again wait for 1 second OnTradeTransaction, and then check again.

I wouldn't call it "scoring" .

 
prostotrader:

If you like it that way, then let there be "scoring", but after the first check, wait again for 1 sec OnTradeTransaction and then check again.

Why wait when you can check on every OnTradeTransaction?

If I understand correctly, OnTradeTransaction skips the requesters only in case of connection failures?

Otherwise, of course, a list of non-collapsed mages/requests should always be saved when exiting the EA.

123456789101112
New comment