I know I'm late to the party on this one. And I'm also new to using the CCanvas library. How does this library (iCanvas) ease the creation of graphical objects? Thanks in advance for your insights.
Probably your icanvas works flawlessy with mql5, i cannot test it. Easy replacement for many things. So to get red on the canvas, vscode shows purple. This applies not only to my icanvas class, but to any graphical output in the tester
Kyle Young Sangster #: I know I'm late to the party on this one. And I'm also new to using the CCanvas library. How does this library (iCanvas) ease the creation of graphical objects? Thanks in advance for your insights.
The main advantage of this library is that it allows you to increase the performance of recalculating Price - Time coordinates into XY coordinates and back by a thousand times compared to using standard functions. This is a serious semantic bug in MQ, which gives many the impression that canvas is very slow. In fact, canvas is the most high-performance visualization technology, including in other programming languages and frontend.
and a canvas is created for the entire window, the size of which automatically changes with the window size. This is very convenient. I am a proponent of using one canvas for the entire window, rather than multiple canvases.
If you really want to learn how to work effectively with canvas, then I advise you to read this thread and delve into the numerous examples in this thread.
How does this library (iCanvas) ease the creation of graphical objects?
Thanks in advance for your insights.
LOVE the second chart in post #18. Spectacular!
I know I'm late to the party on this one. And I'm also new to using the CCanvas library.
How does this library (iCanvas) ease the creation of graphical objects?
Thanks in advance for your insights.
The main advantage of this library is that it allows you to increase the performance of recalculating Price - Time coordinates into XY coordinates and back by a thousand times compared to using standard functions. This is a serious semantic bug in MQ, which gives many the impression that canvas is very slow. In fact, canvas is the most high-performance visualization technology, including in other programming languages and frontend.
It is also enough to add the line
and a canvas is created for the entire window, the size of which automatically changes with the window size. This is very convenient. I am a proponent of using one canvas for the entire window, rather than multiple canvases.
If you really want to learn how to work effectively with canvas, then I advise you to read this thread and delve into the numerous examples in this thread.
https://www.mql5.com/en/forum/412168
The latest version of this library is in the Russian-language codebase:
https://www.mql5.com/ru/code/22164