So, if there's a ChartEvent in the event queue, it shouldn't be queued up a second time. Well, it didn't happen :)
Only CHARTEVENT_MOUSE_MOVE and CHARTEVENT_CHART_CHANGE are not queued. I.e. only these ChartEventevents have a limit of "no more than one in the queue".
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Hello all!
There is a paragraph like this in the help:
So, if there's a ChartEvent in the event queue, it shouldn't be queued up a second time. Well, it didn't happen :)
Then everyone will set the millisecond timer, even if they don't have to...
Come on. You can't take people's responsibility away from them. It only makes them stupid. Do you need it?
Does anyone know the answers to the following questions:
1) how to display multilines (with line break) in one object, e.g. like Label?
2) Why in CChartObjectRectLabel no text is displayed? (or is it supposed to be)?
Doesn't OBJPROP_ZORDER help?
It sort of only affects the routing of mouse events.
Yes, I realised I said the wrong thing and deleted the comment)
Is it possible to prevent the mouse events from passing through the indicator?
On the visible part of the chart overlay pieces from the trend object on the indicator lines, and catch the mouse in these objects.
But do not draw on the whole indicator, but rather redraw only the visible part, otherwise the MT will lie under a huge number of objects.
Well, at least, you can cover two windows in + - half of the window beyond the visible part, then you can redraw less often.
Good afternoon!
Help, good people, I've already racked my brains...
There is a Dll, it has the required function, which returns a pointer to a structure via parameter. In other words, it has a function:
I import it into MQL5 as:
I run through outResult - the first 4 bytes in it are non-zero, i.e. it looks like a Pointer.
Note - question: how to get data at this address in MQL5?
One more thing - I've found a 'useful' trick...
Declare an array, for example, 'int arrTemp[5];'.
Under the debugger all its items equal 0, while during testing they don't.
I spent half a day trying to find out why the connect() function from WinSock library ported from MQL4 does not work.