strange... and monstrous. - page 6

 

I was left with an unpleasant impression of the GetLastError diagnostics...

The brokerage house advertised by the developers has changed the rules again. Now you cannot set an espionage time for pending orders.

And MTS which set the pending orders (so as not to "sweat..." (c) Rinat - analyzing the battlefield) with set expiry time, quietly died in a stupor ;)

error 3 (ERR_INVALID_TRADE_PARAMETERS)...

Is it really difficult to specify the parameter number, or rather detail - wrong price level, stoploss, tprofit? :) There is some specificity of errors in trading functions...

And this parameter, which is handicapped, turns out to be aspiration time... But how does the councillor know that?

;)

 

Crookedness is a condition! ;)

Decided to put a couple of uncomplicated scripts on the hotkeys. And started trading (demo) from the beginning of the month with one click -

What surprised?

Keys don't always respond. i.e. script doesn't always run, key code is kind of swallowed...

Is this the way it's meant to be? Or does it also need to coincide with the coming/not coming of the tick?

DDD

--------------

And the developers don't see the "Mosek" issues - they just crush/ban the innocent...

;)

 
FreeLance:

Crookedness is a condition! ;)

Decided to put a couple of uncomplicated scripts on the hotkeys. And started trading (demo) from the beginning of the month with one click -

What surprised?

Keys don't always respond. i.e. script doesn't always run, key code is kind of swallowed...

Is this the way it's meant to be? Or does it also need to coincide with the coming/not coming of the tick?

DDD

--------------

And the developers don't see the "Mosek" issues - they just crush/ban the innocent...

;)


If they always react, your graph will go up even more steeply, the world economy will not stand for it.

Generally speaking, you have something eating up resources. Maybe the indicators are heavy or something else. Does F3 and F7 respond normally?

 
PapaYozh:


If it always reacts, your chart will go up even more, the world economy will not survive.

Generally, you have something eating up resources. Perhaps the indicators are heavy or something else. Are F3 and F7 responding normally?

Exactly the same. As a simulation, you could put a failed CD in the drive. :)
The MT4 terminal's bottleneck is that it waits for input/output operations with the disk to complete ( and it doesn't matter who performs those operations). Keyboard, mish, any events become inaccessible to it...

Very strange logic.

;)

 

FreeLance:

and the developers don't see the "Mosek" issues at all - just crushing/banning innocents...

My observation is that the developers care about the way the material is presented. That doesn't mean you have to flatter yourself in front of them, but let's just say they don't like to be flamboyant.

I mean, in a subject with excessive ... er... emotional title, they'd hardly have been welcome at the best of times. And now it's hard to expect them to pay much attention to MT4 problems.

 
Candid:

My observation is that the developers care about the way the material is presented. That doesn't mean you have to bow down to them, but let's just say they don't like to be outrageous.

My point is that in a thread with excessive ... er ... emotional name, they would hardly have been worth waiting for at the best of times. And right now it's hard to expect special attention to MT4 problems anyway.

I agree - especially if the server initially has a regular function of throwing in "quotes"... ;)

And as for the terminal, it also reliably protects the server logs from writing trade orders.

Wait for it, don't wait.

Even rebooting does nothing.

On CROWFRE, a similar thread has been started again and mocks the "conspiracy theory".

But, what is a trader supposed to check if the trade flow is busy or Common error?

;)

 

Ran into the following:

Had to convert someone else's bar history files to upload them already in HST MT4 format.

Due to different date format I had to create a format conversion for the standard function.

But the strangest thing is the result of the test.

2010.11.19 17:48:09 String_to_Time EURUSD,M15: 19.11.2010 00:15= 1290125700 int=:1290125700 shift=900
2010.11.19 17:48:09 String_to_Time EURUSD,M15: 19.11.2010 00:00= 1290124800 int=:1290124800 shift=-85500
2010.11.19 17:48:09 String_to_Time EURUSD,M15: 18.11.2010 23:45= 1290210300 int=:1290210300 shift=900
2010.11.19 17:48:09 String_to_Time EURUSD,M15: 18.11.2010 23:30= 1290209400 int=:1290209400 shift=1290209400

It turns out, that not 900 seconds passed from quarter to midnight, but time machine turned on...

On minute intervals -

2010.11.19 17:46:58 String_to_Time EURUSD,M15: 19.11.2010 00:01= 1290124860 int=:1290124860 shift=60
2010.11.19 17:46:58 String_to_Time EURUSD,M15: 19.11.2010 00:00= 1290124800 int=:1290124800 shift=-86340
2010.11.19 17:46:58 String_to_Time EURUSD,M15: 18.11.2010 23:59= 1290211140 int=:1290211140 shift=60
2010.11.19 17:46:58 String_to_Time EURUSD,M15: 18.11.2010 23:58= 1290211080 int=:1290211080 shift=1290211080


And some ticks require. One can imagine the confusion there for the poor progger.

;)

Everyone can check - maybe it's the new build 229?

//+------------------------------------------------------------------+
//| String_to_Time.mq4 |
//+------------------------------------------------------------------+
int start()
{
int old_datetime=D'1970.01.01 00:00';
string fDate="18.11.2010";
string fTime="23:30";
datetime DateTimes=SringtoTimeA( fDate, fTime);
int i_datetime=DateTimes;

Print (fDate+" "+fTime,"= ",DateTimes," int=:",i_datetime
," shift=",i_datetime-old_datetime);
old_datetime=i_datetime;
fTime="23:45";
DateTimes=SringtoTimeA( fDate, fTime);
i_datetime=DateTimes;
Print (fDate+" "+fTime,"= ",DateTimes," int=:",i_datetime
," shift=",i_datetime-old_datetime);
old_datetime=i_datetime;
fDate="19.11.2010";fTime="00:00";
DateTimes=SringtoTimeA( fDate, fTime);
i_datetime=DateTimes;
Print (fDate+" "+fTime,"= ",DateTimes," int=:",i_datetime
," shift=",i_datetime-old_datetime);
old_datetime=i_datetime;

fTime="00:15";
DateTimes=SringtoTimeA( fDate, fTime);
i_datetime=DateTimes;
Print (fDate+" "+fTime,"= ",DateTimes," int=:",i_datetime
," shift=",i_datetime-old_datetime);
//----
return(0);
}
//+------------------------------------------------------------------+
//| Convert string date&time formated DD.MM.YYYY & HH:MM |
//+------------------------------------------------------------------+
int SringtoTimeA(string fDate, string fTime="00:00")
{
string sDD=StringSubstr(fDate,0,2); // Day
string sMM=StringSubstr(fDate,3,2); // Month
string sYYYY=StringSubstr(fDate,6,4);// Year
if (StringLen(fTime)<5) fTime="0"+fTime;
return(StrToTime(sYYYY+sMM+sDD+" "+fTime));
}
//+------------------------------------------------------------------+

 

Even if the function is designed differently.

//+------------------------------------------------------------------+
//| Convert string date&time formated DD.MM.YYYY & HH:MM |
//+------------------------------------------------------------------+
int SringtoTimeA(string fDate, string fTime="00:00")
{
string sDD=StringSubstr(fDate,0,2); // Day
string sMM=StringSubstr(fDate,3,2); // Month
string sYYYY=StringSubstr(fDate,6,4);// Year
string sConcat="";
if (StringLen(fTime)<5) fTime="0"+fTime;
sConcat=StringConcatenate(sConcat,sYYYY,sMM,sDD," ",fTime);
return(StrToTime(sConcat));
}
//+------------------------------------------------------------------+

00-00 in MT4 is the end of the old day or the beginning of a new one?

It turns out, it is the beginning of the old day. Or the day is numbered wrong...

;)

 

No regularities detected... :о)

2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 19.11.2010 00:01= 1290124860 int=:1290124860 shift=60
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 19.11.2010 00:00= 1290124800 int=:1290124800 shift=-82800
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 18.11.2010 24:00= 1290207600 int=:1290207600 shift=-3540
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 18.11.2010 23:59= 1290211140 int=:1290211140 shift=86340
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 18.11.2010 00:00= 1290124800 int=:1290124800 shift=-86340
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 17.11.2010 23:59= 1290211140 int=:1290211140 shift=86280
2010.11.19 19:16:11 String_to_Time AUDJPY,M30: 17.11.2010 00:01= 1290124860 int=:1290124860 shift=1290124860

 

Get in line, you'll be one hundred and fifty.

Reason: