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
Ok, I'll do. Now it is working (I had to remove the GetTickCount lines to get it synced). Thank you.
Good afternoon, Nikolay!
Do you plan to add the creation of coordinate axes to the library?
Good afternoon, Nicholas!
Do you plan to add the creation of coordinate axes to the library?
didn't quite understand the question.

What do you mean?
Canvas is already XY coordinate plane.
Or do you mean scales like in chart?
I don't quite understand the question.
What do you mean?
Canvas is already the XY coordinate plane.
Or do you mean scales like in a chart?
Yes, its own scales
Yeah, their scales.
and what's so hard to do yourself?
It's a matter of design and taste, and everyone has his own.
By the way, this iCanvas library is a light version.
It has 500 lines of code.
My extended, still unfinished, version already has 2500 lines of code.
I will probably publish the extended version, if it will be still relevant and in demand. But it will be a while yet .
and what's so hard to do yourself?
There is not much complicated, but you are a developer, suddenly you plan to write, so why do the same thing unnecessarily
I'll probably post an extended version if it's still relevant and in demand. But it will be a while yet .
Your library will be in demand when it will be oriented to indicators (mainly) in which it is necessary to display large data sets (e.g. ticks between bars).
display large data arrays (e.g. ticks between bars).
Your library will be in demand when it is focused on indicators (mostly) in which you need to
display large data arrays (e.g. ticks between bars).
Of course.
And this is among other things.
In fact, the range of solved problems is much wider.
This includes creation of your own charts, your own GUI, creation of indicators with dynamically changing number of lines or dynamic timeframes, multi-window indicators and Expert Advisors, visualisation of various data, etc.
You can even write your own trading platform inside MT with window detachment.
Of course.
And this is among them.
In fact, the range of solvable tasks is much wider.
This includes creating your own charts, your own GUI, creating indicators with dynamically changing number of lines or dynamic timeframes, multi-window indicators and Expert Advisors, visualisation of various data, etc.
You can even write your own trading platform inside MT with window detachment.
A cool example in the attachment.
I, for example, do not need a terminal in trading at all.
For 7 years I have only 2 indicators written by me, on which I do not trade, but only analyse and calculate.
I only do analyses and calculations.
You are trying to go from the complex..., but it is necessary to go from the simple.
Look at the first posts, there are "why", "beautiful, but not necessary", etc.
Make it simple.
An indicator template with axes, with the ability to scale (for example, spread between two instruments based on tick history) and the demand for your library will increase many times.
will increase in times.
Cool example in the attachment.
I, for example, do not need a terminal in trading at all.
For 7 years I have only 2 indicators written by me, on which I do not trade, but I do not use them.
I only do analyses and calculations.
You are trying to go from complicated to simple.
Look at the first posts, there are "why", "beautiful but not necessary", etc.
Keep it simple.
An indicator template with axes, scalability (e.g. spread between two instruments based on tick history) and demand for your library.
will increase in times.
I was obsessed with hundreds of indicators and Expert Advisors for 6 years, going from simple to complex.
As a result, I came to the complex one, which is what I have been doing for the last 8 years, making only one indicator and one Expert Advisor.
This library is just a hobby and I make it exclusively for myself and because the existing tools did not suit me.
The version in KB is a very neutered version of my version. The main thing is that it does not have smooth graphics, while mine does.
If I published my version, the demand would soar many times. I just don't need it.