Canvas vs Labels - page 11
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
So, here are the results of the comparison of the displays without and with refresh rate limitation.
The sources for repeating these measurements can be downloaded here:https://www.mql5.com/ru/code/33898
I am also publishing the results of the comparison in the terminal chart, for which I have specially written an expert working in the loop, both in the chart and in the tester.
Download its source code from KB:https://www.mql5.com/ru/code/33898
Results comparison table
So, here are the results of the comparison of the displays without and with refresh rate limitation.
You can download the source code for repeating these measurements here:https://www.mql5.com/ru/code/download/33898/chartdisplay.mqh and here: https://www.mql5.com/ru/code/download/33898/canvasvslabelstester.mq5.
Where's the limitFps?
Where are the limitFps?
Download files in\MQL5\Experts\canvas-vs-labels\measurement\cyberdev\ and \MQL5\Experts\canvas-vs-labels\measurement\ in KB. To limit fps, set limit_fps to true in the input parameters. file: CanvasVsLabels.mq5. How to run the test is shown above. And there is a description in KB.
Download files in\MQL5\Experts\canvas-vs-labels\measurement\cyberdev\ and \MQL5\Experts\canvas-vs-labels\measurement\ in KB. To limit fps, set limit_fps to true in the input parameters. file: CanvasVsLabels.mq5. How to run the test is shown above. And there is a description in KB.
The question was specifically asked about limitFps.
And I don't need it, it's clear to me long time ago that your fantasies don't correspond to reality. The whole interest is to see where you are going wrong again.
The question was specifically asked about limitFps.
This is an update limit. It is made so that the display updates do not exceed the minimum refresh rate acceptable to the human eye. Hence the performance gain in Kanvas even compared to Labels. And if this limitation is applied to the Labels, such a display flies at all. The measurement results are above. Plus, I've mentioned it before. I don't understand what's not clear to you or, what's wrong with you...?
How can I manually limit kanvas refresh rate in the visualizer?
So that at slow speed the picture is refreshed in real time, and at fast speed it doesn't slow down the test?
Right now canvas (if it is updated on every tick) is really slowing down the whole visualization (profiling shows 80-90% of rendering time). I twisted with configurable pause in seconds, but it's a crutch, limiting functionality (picture updates rarely even at slow speed).
What to bind to so it doesn't refresh too often? GetMicroseconds?
Which functions to skip?
How can I limit the kanvas refresh rate in the visualizer in a human way?
So that at slow speed the picture is refreshed in real time, and at fast speed it doesn't slow down the test?
Right now canvas (if it is updated on every tick) really slows down the whole visualization (profiling shows 80-90% of rendering time). I twisted with configurable pause in seconds, but it's a crutch, limiting functionality (picture updates rarely even at slow speed).
What to bind to so it doesn't refresh too often? GetMicroseconds?
What functions to skip?
In the MT5 tester, the timer works, you can set it to 60 sec and it will update once per minute according to tester time)
This is an update limitation. It is made so that the display updates do not exceed the minimum refresh rate acceptable to the human eye. Hence the performance gain of Canvas, even compared to Labels. And if this limitation is applied to the Labels, such a display flies at all. The measurement results are above. Plus, I've mentioned it before. I don't understand what's not clear to you or, what's wrong with you...?
Did I ask what it is?