Demonstrating something doesn't mean scoring a goal. If I only made statements, I would have "demonstrated" my 25 goals at least a year ago. In principle, I have demonstrated them, but only in the market:
//---
Therefore, your goals are so far past my goal. Only what is available to the community counts as a goal.
The current score is 18 to 0 in my favour. And that's just by the number of articles. You, on your part, have started counting goals in your favour by functionality. And if you consider that I publish sources, then one of my goals can be counted as two (minimum).
Therefore, the score is at least 36 : 0 in my favour.
If you want to reduce the number of my goals to 18 (minimum), then publish the sources. Otherwise I don't know now how you will catch up with me. ;)
Anatol, question: will there be a "standard" possibility to override the mutual location of objects in composite elements, as well as changing their sizes?
For example, in order to compactly pack sliders into small panel sizes, I had to change/add slider methods.
Anatol, question: will there be a "standard" possibility to override the mutual location of objects in composite elements, as well as changing their sizes?
For example, in order to compactly pack sliders into small panel sizes, I had to change/add slider methods.
But that's not very practical in terms of compatibility with future updates.
Perhaps I missed something, or on the contrary I haven't got there yet ))) But my slider is constantly glitching, when creating the slider runs away to the rightmost value even if it was set as the average between the upper and lower. However, the value shows what was set when defining it. And after that, when trying to rotate it in any way, the value changes either to the extreme minimum or to the extreme maximum.
Perhaps I missed something, or on the contrary I haven't got there yet ))) But my slider is constantly glitching, when creating the slider runs away to the rightmost value even if it was set as the average between the upper and lower. However, the value shows what was set when defining it. And after that, when trying to rotate it in any way, the value changes either to the extreme minimum or to the extreme maximum.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
...
So the score is not dry ... ;)
Demonstrating something doesn't mean scoring a goal. If I only made statements, I would have "demonstrated" my 25 goals at least a year ago. In principle, I have demonstrated them, but only in the market:
//---
Therefore, your goals are so far past my goal. Only what is available to the community counts as a goal.
The current score is 18 to 0 in my favour. And that's just by the number of articles. You, on your part, have started counting goals in your favour by functionality. And if you consider that I publish sources, then one of my goals can be counted as two (minimum).
Therefore, the score is at least 36 : 0 in my favour.
If you want to reduce the number of my goals to 18 (minimum), then publish the sources. Otherwise I don't know now how you will catch up with me. ;)
Anatol, question: will there be a "standard" possibility to override the mutual location of objects in composite elements, as well as changing their sizes?
For example, in order to compactly pack sliders into small panel sizes, I had to change/add slider methods.
Screenshots of the MetaTrader trading platform
EURUSD, D1, 2016.12.27
MetaQuotes Software Corp., MetaTrader 4, Demo
But this is not very practical in terms of compatibility with future updates.
Anatol, question: will there be a "standard" possibility to override the mutual location of objects in composite elements, as well as changing their sizes?
For example, in order to compactly pack sliders into small panel sizes, I had to change/add slider methods.
But that's not very practical in terms of compatibility with future updates.
I've already answered this question for you.
Forum on trading, automated trading systems and testing trading strategies
Discussion of the article "Graphical Interfaces III: Simple and Multifunctional Buttons (Chapter 1)"
Anatoli Kazharski, 2016.09.29 18:07
I will make it so that you can change any property of elements already after creation.//---
But not everything at once. All the most important things first. Subtle settings last (lowest priority).
I've already answered that question for you.
//---
But not all at once. The most important things first. Fine tuning last (lowest priority).
Perhaps I missed something, or on the contrary I haven't got there yet )))
But my slider is constantly glitching, when creating the slider runs away to the rightmost value even if it was set as the average between the upper and lower. However, the value shows what was set when defining it. And after that, when trying to rotate it in any way, the value changes either to the extreme minimum or to the extreme maximum.
Can you suggest something?
Perhaps I missed something, or on the contrary I haven't got there yet )))
But my slider is constantly glitching, when creating the slider runs away to the rightmost value even if it was set as the average between the upper and lower. However, the value shows what was set when defining it. And after that, when trying to rotate it in any way, the value changes either to the extreme minimum or to the extreme maximum.
Can you suggest something?
Try the latest version of the library:
EasyAndFastGUI - library for creating graphical interfaces
Dear Anatoli Kazharski
Thanks for your sharing, it is very advanced.
I am tring to compile in MT4 MetaEditor,the following errors occured. I don't know what is wrong for me, i am a beginner.
Looking forwards to your answer.