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
Have the causes of the blinking been identified?
What blinking?
I don't have any blinking.
what blink?
I don't have any blinking.
Tested the library - convenient and functional!
two questions:
1. is there a ready implementation of a segment ending with an arrow? (there are examples under C++ http://www.cyberforum.ru/qt/thread1534114.html it is not a problem to port, but maybe there is a ready-made one and I didn't find it ;) )
2. changing the chart just clears the whole canvas? - if yes, it's very inconvenient, if not - I haven't figured it out, I need an example
I think it's line 349, recreate canvas, which is now commented out
I fixed that when I found that it was causing a freeze. But there was no blinking, just iCanvas stopped working.
Fixed a small bug in version 1.34 that caused the sine example not to work.
Tested the library - convenient and functional!
two questions:
1. is there a ready implementation of a segment ending with an arrow? (there are examples under C++ http://www.cyberforum.ru/qt/thread1534114.html it is not a problem to port, but maybe there is a ready-made one and I didn't find it ;)) )
2. changing the chart just clears the whole canvas? - if yes, it's very inconvenient, if not - I haven't figured it out, I need an example
Thanks, Igor.
1. No, I haven't implemented it yet. With unsmoothed lines it is quite easy to do it. There are a lot of things I haven't implemented, and a lot of things I haven't posted yet.
2. No, of course not. Why do it. In my programs, when I change the chart, I forcibly redraw everything when the coordinates are tied to time and price, not to screen pixels. How could it be otherwise when price-time changes coordinates.....
Actually, the main beauty of this library is its speed.
If you try to do everything I do in iCanvas in CCanvas, the speed will drop significantly.
The main reason is that you will have to use terribly slow asynchronous functions, such as ChartXYToTimePrice(), which takes about 5000 microseconds. That's an incredibly long time.
The main goal of iCanvas was just to get away from these very expensive functions.
https://www.mql5.com/ru/forum/1111/page2099#comment_6310826
Please note that it is better not to use the Line function in CCanvas when the coordinates of two points are formed not guaranteed within the screen. There is a serious bug there.
result of execution:
Last version 1.35
https://www.mql5.com/en/code/27733I fixed this when I found that there was a freeze happening because of this. But there was no blinking, just iCanvas stopped working.