Discussion of article "Graphical Interfaces III: Simple and Multi-Functional Buttons (Chapter 1)" - page 2

[Vladimir Karputov]

Citizens, please, discussion on the topic of the article. If there are no questions to the article, please start a new topic or write questions from beginners in the existing one.

[Anatoli Kazharski]

Sergey Pavlov:

...

I just answered the questions. And I don't want to argue about anything.

And all that you wrote about irritation, whether I am satisfied with something or not, and so on, so it's just your speculations and delusions. So don't start "half a turn" and don't reply to messages addressed not to you.

It is everyone's personal business to "pick" in the published code or not. For those who want to learn how to do such things, it makes sense to "dig". For those who want to use a ready-made code library, it makes sense to wait until all the articles in the series are published.

[Sergey Pavlov]

Anatoli Kazharski:

... and do not reply to messages not addressed to you ....

Obey and obey.

I didn't notice when the forum became a private place of communication.

[Реter Konow]

Anatoly, I once again express my respect and admiration for your work. Your articles are written very professionally and very detailed. They are undoubtedly of great value from the point of view of teaching novice developers. Your unselfishness and openness also inspires respect. But what should I do if I find your approach ineffective? Keep silent? Write my own articles?

If I write my own articles, they will be no more than five. In them I will fully disclose my technology (which is much easier to understand because there is no OOP in it) and it will be immediately picked up by experienced programmers (especially if I attach written codes to the articles). Do you need additional competition in articles on the interface?

If you say I'm comparing early, then I accept that you're not ready yet and won't compare results until you show the full power of your approach. However, should I sit quietly and not show anyone, anything? I think not. After all, you and I live in a competitive world).

[Anatoli Kazharski]

Реter Konow:

Anatoly, I once again express my respect and admiration for your work. Your articles are written very professionally and very detailed. They are undoubtedly of great value from the point of view of teaching novice developers. Your unselfishness and openness also inspires respect. But what should I do if I find your approach ineffective? Keep silent? Write my own articles?

Do the same things you are doing now. Express your opinion. If you write articles, I will definitely read them. It is more interesting to communicate with code and schemes.

Stories about "I have something, but I won't tell you how it is implemented" are not interesting.

If I write my own articles, there will be no more than five of them. In them I will fully disclose my technology (which is much easier to understand because there is no OOP in it) and it will be immediately picked up by experienced programmers (especially if I attach written codes to the articles). Do you need additional competition in articles on the interface?

There is no problem with that. You can publish anything you want. I'd be interested to see that too. ))

If you say I'm comparing early, then I accept that you're not ready yet and won't compare results until you show the full power of your approach. However, should I sit quietly and not show anyone, anything? I think not. After all, you and I live in a world of competition).

Act according to the principle: "First do, then say". ))

[Реter Konow]

I can hardly be reproached for inconsistency. With a finished result, I am ready to demonstrate it, and if it is interesting, I can start talking about it. With the opposite logic, I would start telling or teaching others much earlier, without being able to show them the result that awaits them at the end of the training, because I have not yet reached that end myself.

[Anatoli Kazharski]

Реter Konow:
I can hardly be reproached for inconsistency. With a finished result, I am ready to demonstrate it, and if it is interesting, I can start talking about it. With the opposite logic, I would start telling or teaching others much earlier, not being able to show them the result that awaits them at the end of training, because I have not reached that end yet.

I am interested in your result. If you have a desire to demonstrate it, start.

The degree of interest in your work is higher the more information you provide about it:

1. Just screenshots and videos are the least interesting.
2. More interesting would be (if you don't want to demonstrate your code) compiled demo versions (free) of MQL applications published in the Market. This way you can test MQL-applications with a graphical interface made with the help of your library.
3. The most interesting is the open code of your library with a detailed description and explanation of how to use it.

I work in the third format. The format in which you are willing to demonstrate your work is up to you.

If you want, you can do it in the discussion threads of my articles. But you also have the opportunity to open your own personal thread on the forum. You can even try to hold a vote, based on the results of which you will evaluate the degree of interest in your work.

[Реter Konow]

Thank you for your suggestion and interest. I am currently in the final stages of developing my project. I think that after that I will have more free time to communicate on the forum.

For now I will publish screenshots, then videos, and after the project is completed, I will put the Expert Advisor for sale, and everyone who downloaded it will be able to test the trial version.

At the same time, I am ready to highlight the nuances of my work especially for you (as for my respected colleague), in private messages.

If you have any specific questions, please ask.

Sincerely yours, Peter.

[Artyom Trishkin]

Anatole, can't you dynamically change the colour of the buttons? Imagine a button to move a stop to breakeven. As long as the price has not reached the possibility to move the stop to the CU, the button has the same colour, as soon as it is possible to move the stop to breakeven, the button is highlighted in a different colour.

Now there is an opportunity only to block/unblock it, which is not very beautiful - when blocking the button, the user sees that it is not available at all, but when changing its unblocked colour - it is already visible that with one colour the result of pressing it will be zero, and with another colour - the result of pressing it will be the transfer of stop to breakeven.

[Anatoli Kazharski]

Artyom Trishkin:

Anatole, can't you dynamically change the colour of the buttons? Imagine a button to move a stop to breakeven. As long as the price has not reached the possibility to move the stop to the CU, the button has the same colour, as soon as it is possible to move the stop to breakeven, the button is highlighted in a different colour.

Now there is an opportunity only to block/unblock it, which is not very beautiful - when blocking the button the user sees that it is not available at all, but when changing its unblocked colour - it is already visible that with one colour the result of pressing it will be zero, and with another colour - the result of pressing it will be the transfer of stop to breakeven.

I will make it so that it is possible to change any property of elements already after creation.