Errors, bugs, questions - page 2283

 
Administrators and Service Desk please pay attention to the topic with the Bughttps://www.mql5.com/ru/forum/278253
 

There is a problem when connecting to the storage. How to fix it?

 

Bild 1881. Difficulties with the choice of colour.

 
Vladimir Karputov:

SerVisdesk was closed because of endless questions from beginners and schoolboys, because users PRACTICALLY never describe the full problem and had to be plucked out of them with pincers.

Now it's like this: if there's a problem, create a separate THEME, with a COMPLETE description, with code WHICH CAN COLLECT and reproduce the problem.

You may have misread the question I was asking, I wasn't asking why they closed the service-desk, I was asking why they removed the entire request history from there and if it's retrievable now.
 

When renaming a graphical object, the events described in the ObjectSetString function note are not generated

int OnInit()
{
    EventSetTimer( 5 );
    ChartSetInteger( 0, CHART_EVENT_OBJECT_CREATE, true );
    ChartSetInteger( 0, CHART_EVENT_OBJECT_DELETE, true );
    return INIT_SUCCEEDED;
}
void OnTimer()
{
static int i = 0;
    string name = "ABC";
    switch ( ++i ) {
    case 1: Print( __FUNCTION__, ":", i ); if ( !ObjectCreate(    0, name, OBJ_VLINE, 0, D'2018.08.24', 0 )) Print(GetLastError()); ChartRedraw(); break;
    case 2: Print( __FUNCTION__, ":", i ); if ( !ObjectSetString( 0, name, OBJPROP_NAME, name + "2"       )) Print(GetLastError()); ChartRedraw(); break;
    case 5: Print( __FUNCTION__, ":", i, ":", GetLastError()); EventKillTimer();                                                                   break;
    }
}
void OnChartEvent(const int id, const long &lparam, const double &dparam, const string &sparam)
{
    Print( __FUNCTION__, ":", EnumToString((ENUM_CHART_EVENT)id ));
}

Result:
2018.09.10 04:23:51.542 Test (EURUSD,H4) OnTimer:1
2018.09.10 04:23:51.549 Test (EURUSD,H4) OnChartEvent:CHARTEVENT_OBJECT_CREATE
2018.09.10 04:23:56.534 Test (EURUSD,H4) OnTimer:2
2018.09.10 04:24:11.553 Test (EURUSD,H4) OnTimer:5:0

Expected:
2018.09.10 04:23:51.542 Test (EURUSD,H4) OnTimer:1
2018.09.10 04:23:51.549 Test (EURUSD,H4) OnChartEvent:CHARTEVENT_OBJECT_CREATE
2018.09.10 04:23:56.534 Test (EURUSD,H4) OnTimer:2
Test (EURUSD,H4) OnChartEvent:CHARTEVENT_OBJECT_DELETE
Test (EURUSD,H4) OnChartEvent:CHARTEVENT_OBJECT_CREATE

2018.09.10 04:24:11.553 Test (EURUSD,H4) OnTimer:5:0

 
Alexey Navoykov:
You may not have read the question I asked carefully. I didn't ask why they closed the service-desk. I asked why they deleted the entire application history from there and whether it is possible to find it now.

A lot of relevant information has been destroyed.

 
Why is the SSD constantly being accessed during Optimisation (the light flickers at a high frequency)?
 
fxsaber:
Why is the SSD constantly being addressed (light flickers at high frequency) during Optimisation?
Genetics?
 
Slava:
Genetics?

Total overkill. 8 cores. The EA itself doesn't write or read anything. Custom symbol by real ticks.

 
fxsaber:

Total overkill. 8 cores. The EA itself doesn't write or read anything. Custom symbol based on real ticks.

Well, ticks are not stored in the memory. They are downloaded as needed, in parts, as far as I understand.

Reason: