Discussion of article "Graphics in DoEasy library (Part 89): Programming standard graphical objects. Basic functionality"
If yes, where is it described?
- The Print that causes this warning is temporary. That's why it is written as Print. Those that are needed in the library are written as ::Print. This one will be removed soon. PS: for me this is one way to know where the temporary stoppers are located - so I don't have to look for them for a long time.
- What do you mean by "logging" ?
1. I am a beginner here. What is ::Print? Where to read about it?
2. "logging" is journaling, i.e. generating information about events and sending them somewhere (to the Expert Advisor's log, file ...). It is a necessary thing for complex software. I have seen some rudiments of it in the texts of basic objects.
2. "logging" is journaling, i.e. generating information about events and sending them somewhere (to the Expert Advisor's log, file ...). It is a necessary thing for complex software. I have seen some rudiments of it in the texts of basic objects.
2. "logging" is journaling, i.e. generating information about events and sending them somewhere (to the Expert Advisor's log, file ...). It is a necessary thing for complex software. I have seen some rudiments of it in the texts of basic objects.
There is a class CMessage for this purpose.
:: before the function name is an operation of context resolution.

- www.mql5.com

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
New article Graphics in DoEasy library (Part 89): Programming standard graphical objects. Basic functionality has been published:
Currently, the library is able to track standard graphical objects on the client terminal chart, including their removal and modification of some of their parameters. At the moment, it lacks the ability to create standard graphical objects from custom programs.
Compile the EA and launch it on the chart.
First, create a vertical line by clicking on a chart while holding down Ctrl, have a look at the line ID and at how object properties change when moving the line along the chart. If we re-create the same line, we get the error message in the journal.
Next, create an equidistant channel, see its ID value and check how changes in the properties of its three pivot points are tracked:
Author: Artyom Trishkin