Discussion of article "Graphical Interfaces X: Text selection in the Multiline Text box (build 13)" - page 2
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
Very much in line with my experience as well.
But Anatoly, unlike me, sees the "big picture" in advance - that's why he lays down for further development.
I sin that I don't make "unnecessary movements" in favour of the speed of solving the current task....
But how much time they could save in the future!
That's why I sincerely admire this library, its filling with goodies is consistent and uninterrupted, and what is very important - consistently.
It means that the project is not created on the knees, but with a well thought out goal and preliminarily outlined possibilities.
Thanks to Anatoly and MetaQuotes for this extension!
If there is not enough support to continue the project - we will knock a bowl! :)
This is a super project also in terms of documentation quality.
For me this is an unattainable level of design in MQL (
...
This is a super project also in terms of documentation quality.
....
The current series of articles can be considered only as technical documentation. For using the library in your MQL-projects such a voluminous and detailed description is of course super redundant. To quickly understand the possibilities and methods for designing your own graphical interfaces, it is now easier to open the file of the control of interest and read the class content in the lists ofpublic methods.
I will try later (after the release) to show very briefly how to use all this in one article. Perhaps, I will make the help in the same style as MQL-documentation.
Okay, I won't distract you. )
You have a great opportunity to read articles on this topic and even use the solutions posted in the source code easily and simply adapting them to your scheme.
You can publish the results on your blog. I am following your publications. ;)
Thank you for your attention to my publications.
Unfortunately, I cannot use your developments in my codes. It is technically impossible. I follow the so-called "principle of universality", i.e. I constantly compress the code, reduce the number of methods, destroy everything I can do without. I try to combine each function with a block performing a set of similar tasks and integrate it into it. In the end, I create several large mechanisms that work with the kernel (common memory containing all the information of the GUI) in different ways. That is, any functions taken from outside will go through this "meat grinder" until their idea essence is extracted, which will have to pass the test of relevance of its presence in the general mechanism of the graphics engine, and if it proves its worthiness, it will be integrated with a couple of additional lines of code.
All in all, it will be sacrilege to your labour, which I sincerely respect.
...
Unfortunately, I cannot use your developments in my codes. It's technically impossible.
...
Well, why can't you? Yes, you can. Perhaps you just don't know how, but that's another matter. )
P.S. Everything you describe as a very complex process is easily and simply solved with the OOP approach. In the release of my library all this will be more clearly presented.
Why can't you? Yes, you can. Maybe you just don't know how, but that's another matter. )
I am interested in your mechanism of a drawn multiline input field. Later I will study it in more detail, and perhaps your solutions will help me to understand the principles of its work faster and make my analogue. I don't exclude it, though I have always developed everything myself. But, sometimes you can do something wrong. )
In any case, thank you for sharing the fruits of your talent free of charge).
My tables are not finished, but the example you demonstrated works the same way. .... Of course, not everything works perfectly yet... Adding columns and columns is not implemented yet. ...
That is, the tables are not finished, it does not work perfectly, a lot of things are not implemented, and yet it works exactly the same. Amazing. )
And apart from the buttons over the years, is there anything else implemented that already works?
...
Anyway, thanks for gratuitously sharing the fruits of your talent :)
P.S. Everything you describe as a very complex process is easily and simply solved with the OOP approach. In the release of my library all this will be more clearly presented.
My task is a bit more complicated, that's probably why I find everything more complicated. I want to make a constructor, bringing the labour-intensive GUI creation down to the level of "lazy-no-learner-hacker".
And that's really hard.))
My task is a bit more complicated, that's probably why I find everything more complicated. I want to make a constructor, bringing the labour-intensive GUI creation down to the level of "lazy-no-learner-no-freeloader".
And that's really hard.))
Yes, not easy. ))
And what do you mean by "designer" ? How do you see him ? What should it be like in your opinion?
That is, the tables are not finished, it works non-ideally, a lot of things are not implemented, and yet it works just the same. Amazing. )
And apart from the buttons over the years, is there anything else implemented that already works?