MetaTrader 4 Build 529 beta released with new compiler - page 117
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
The problem is solvable. What we're trying to do is make sure that the graphics in four are identical to those in five. So that we can take Friday's code and apply it to F4 without changing it.
Let's have your example, which doesn't work as it should.
Let's have a chat in the service desk. You point the finger and say "this is the way it should work in this place, not the other way". We argue against it. Or we accept and make corrections.
I wrote above all my arguments, including function code and its call, people here understood me and confirmed the problem, and you want to argue more :) it made me smile...
Here is my argument https://www.mql5.com/ru/forum/147679/page114#878619 and here are people's arguments https://www.mql5.com/ru/forum/147679/page114#878702 and https://www.mql5.com/ru/forum/147679/page114#878740 look around the thread, it's not three cases, plus who else is being silenced...
The problem is solvable. What we're trying to do is make sure that the graphics in four are identical to those in five. So that we can take Friday's code and apply it to F4 without changing it.
Let's have your example, which doesn't work as it should.
Let's have a chat in the service desk. You point the finger and say "this is the way it should work in this place, not the other way". We argue against it. Or we accept and make corrections.
The problem remains. Although the hopping of graphical objects during selection is resolved, it is still chaos on the graphics.
Let me describe in detail: The fact that the old version of the terminal, when you bind the object to the upper right corner, say at the point 15x20, it was tied to this point for his upper right corner. At the moment (build 558), it binds to the upper left corner, but only if the modification of its properties comes from the program. If we create the object manually and modify the properties, everything is fine.
The same applies to the other corners.
Above I've written all the arguments, including the function code and its call, people here have understood me and confirmed the existing problem, and you want to debate more :) it made me smile...
Here is my argument https://www.mql5.com/ru/forum/147679/page114#878619 and here are people's arguments https://www.mql5.com/ru/forum/147679/page114#878702 and https://www.mql5.com/ru/forum/147679/page114#878740 look around the branch, it's not three cases, plus who else is silent...
We don't know with what parameters you call the function whose code you presented.
Again, give us your example with your call to that function! If this is difficult for you, we will solve other problems in the meantime
The problem remains. Although it has been solved the jumping of graphical objects when selecting, it is still chaos on the graph.
Let me describe in detail: The fact that the old version of the terminal, when you bind the object to the upper right corner, say at 15x20, it was attached to this point for its upper right corner. At the moment (build 558), it binds to the upper left corner, but only if the modification of its properties comes from the program. If we create the object manually and modify the properties, everything is fine.
All the same applies to other corners.
I repeat. We do what we do in five. Be kind enough to apply one more anchor point - indicate where in the object is the "anchor" point of the object. In your case, the top right corner of the object.
We don't know with what parameters you call the function whose code you presented.
Again, give us your example with your call to this function! If this is difficult for you, we will solve other problems in the meantime
In a function call, all parameters are written in the call itself, I even gave you the function parameters.
And whether you'll fix it or not, it doesn't make much difference to me, you can leave it as it is...
Yesterday I struggled with the bmp picture and still could not load it on the chart, and I do not know whether this point works or not yet ...
What's up?
ObjectSet (label_name,OBJPROP_BMPFILE ,euro );You have to set the string parameter! Use ObjectSetString
I have an EA that is not finished yet. I'm writing it to order. I'm writing it in beta, considering that it works in 509th as well. Until the 557th build the EA worked in the tester (if we don't count graphical objects for decoration). Today I updated the Expert Advisor to build 558 in the new terminal for testing in visual mode. Not a single trade. I looked into it - it does not open in start(). In general. First thing I wrote in the start is Print("Hi !!!"); I have no such an entry in the journal. It gets into init() - messages come out of it. In the 509th everything works.
How to be? I have no right to pass the Expert Advisor - it is made to order. We have to find the reason for the failure in the 558th build.
Have you tried to put the EA on the chart (not in the strategy tester)? Are there any messages in the log?
PS. The problem has been reproduced. Wait for the next build with a fix.
Yesterday I struggled with the bmp picture and failed to load it onto the chart, and I don't know if it works or not yet ...
There is no description of error 4024 in the help
No one has answered whether this functionality works or not ...
There is no description of error 4024 in the help
1. answered two posts above
2. See stdlib.mq4 file in the Libraries folder (documentation is not yet complete)
What function and with what parameters did you call before getting this error?