Canvas vs Labels - page 12

New comment
 
Andrey Khatimlianskii:

How can I limit the kanvas refresh rate in the visualizer in a human way?

So that on slow speed the picture is updated in real time, and on 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?

Which functions to skip?

Andrey I already wrote about it here more than a year ago.

It works quite well.
Here's a live video (just two kanvases):

I just need to add that in the tester the CHARTEVENT_CHART_CHANGE event doesn't work,

so I include the following into canvas forming block (when using iCanvas):

void BildParabolas() {
   if(Canvas.tester) ChartChanged();
   static uint lastCalc=0;
   uint cur=GetTickCount();
   if (cur-lastCalc<17) return;
...

And here's part of the code in OnCalculate from the indicator that's on the gif:

static uint lastCalc=0; 
if (Canvas.tester) {
      uint cur=GetTickCount();
      if (cur-lastCalc>17) {
         lastCalc=cur;
         BildParabolas();
         menu.Draw();
      }
   }

 
Dmitry Fedoseev:
it's obvious to the naked eye that kanvas is significantly slower


 
Taras Slobodyanik:

In the MT5 tester, the timer works, you can set it to 60 sec and it will update once a minute at the tester time)

About the pause crutch I wrote, it doesn't work.

 
Nikolai Semko:

Andrei, I wrote about it here over a year ago.

It works quite well.
Here's a live video (just two kanvases):

Looks a bit slow, as for maximum speed.

Thanks, I'll try via GetTickCount!

 
Andrey Khatimlianskii:

Looks a bit slow for maximum speed.

Thanks, I'll try via GetTickCount!

No it's not the maximum. It's very sensitive in front of the maximum.
Here's the maximum:

 
Andrey Khatimlianskii:

Looks a bit slow for maximum speed.

Thanks, I'll try using GetTickCount!

Also, so that there is no bias with respect to the chart itself, we should try experimenting with OBJ_BITMAP instead ofOBJ_BITMAP_LABEL. To bind to time and price instead of XY coordinates.
I still want to try it, but I cannot make it. In this case we will have to make the canvas larger than the window size and change the control logic. The code may have a significant speed advantage due to not having to redraw the whole canvas, but only a smaller part of it, if the vertical scale stays the same. In any case, it won't be annoying to see the kanvas unbalanced with the main graph when moving fast.

 
Nikolai Semko:

No it's not the maximum. It's very sensitive in front of the maximum.
That's the maximum:

Is that "all ticks"?! If so, cool. I'll check it.


Nikolai Semko:

Also, so that there is no bias in relation to the chart itself, we should try experimenting with OBJ_BITMAP instead ofOBJ_BITMAP_LABEL. To bind to time and price instead of XY coordinates.
I all want to try it, but I cannot make it. In this case we would have to make the canvas larger than the window size and change the control logic. Perhaps there will be a speed gain. Anyway, the unbalanced canvas and the main chart will not be breaking the eye when the motion is fast.

I have a simple panel. No link to the chart.

 
Andrey Khatimlianskii:

I have a regular dashboard. There's no link to the chart.

ah, well, that's fine then.
I have one canvas on my hypha too, and it's the panel that eats up the least amount of resources, because I don't have to redraw it as often and catch the moment a new bar comes in.

 
Andrey Khatimlianskii:

Is that "all tics"?! If so, cool. I'll check it out.

No it was minute OHLC on 3 minutes. But I checked on all ticks. The picture is almost the same. Because kanvas redrawing in this case is not tied to ticks, but only to actual time(not tester time). I.e. the higher speed is, the lower frame density is. But to the eye the difference is not visible.

 
Yeah... The animated gifs are certainly a strong argument.
1...56789101112131415161718
New comment