Discussion of article "Graphical interfaces X: New features for the Rendered table (build 9)"

 

New article Graphical interfaces X: New features for the Rendered table (build 9) has been published:

Until today, the CTable was the most advanced type of tables among all presented in the library. This table is assembled from edit boxes of the OBJ_EDIT type, and its further development becomes problematic. Therefore, in terms of maximum capabilities, it is better to develop rendered tables of the CCanvasTable type even at the current development stage of the library. Its current version is completely lifeless, but starting from this article, we will try to fix the situation.

Rendered table with a selected row looks the following way:

Fig. 3. Demonstration of selecting and deselecting a row of the rendered table.

Fig. 3. Demonstration of selecting and deselecting a row of the rendered table.

Author: Anatoli Kazharski

 
Thank you very much for making animated examples of how the elements work. That's great :)
 
The solution with the text in the column changing its width is very nice. The scrolling of the drawn table is great too. Impressed.

I remember in one of your articles you said that you will make the table on the canvas interactive. I must say that you know how to achieve your goals).

Can you tell me about further plans of the library development? I am very interested.

Thank you.
 
Реter Konow:
The solution with the text in the column changing its width is very nice. The scrolling of the drawn table is great too. Impressed.

I remember in one of your articles you said that you will make the table on the canvas interactive. I must say that you know how to achieve your goals).

Can you tell me about further plans of the library development? I am very interested.

Thank you.

The last articles are the second stage of the library development. All the elements will eventually be drawn and provided with all the necessary functionality.

In the next article there will be some more updates for the drawn table and optimisation of algorithms of some methods.

 
Anatoli Kazharski:

The last articles are the second stage of the library development. All the elements will eventually be drawn and provided with all the necessary functionality.

I have no doubt that you can do all this.

However, I have a question about creating a drawn GUI. Don't you think it requires a completely different technology than the one used in your library?

After all, if I am right, you will have to rewrite almost everything you have done before.

A different technology requires a different approach and different solutions. Your table on the canvas now is just a special case of a new technology implemented inside an old technology. In my practice, such things happen all the time, and usually indicate the beginning of a new stage and a new global redesign. From that moment, the new technology starts to conquer its territory, breaking and remaking all the previous solutions and approaches.

This is such an "alarming" sign of the sudden appearance of a new approach inside an old, but stable and fully working development. )

I've gone through this many times and without mentality, I'm just sharing my experience.

Perhaps you will somehow manage to avoid painful redoing of everything done before and the new technology will come to your library easily and freely, saving you from having to pay a high price for it with your labour and time.

I sincerely wish you this, if only because it will be an invaluable example for me, which will turn my worldview).

Good luck.

 
Реter Konow:
...

Perhaps you can somehow avoid the painful redoing of everything that has been done before and the new technology will come to your library easily and freely, saving you from having to pay a high price for it with your labour and time.

The chosen scheme turned out to be a good one. I have already tested the technology of rendering elements in it, everything works very well. In the next article you will see a very good example demonstrating it.
 
That's good. Yes, I can imagine how hard it is to design such articles. Especially when you are involuntarily restricting yourself in some global refactoring with the codes posted on the resource.
 
Igor Volodin:
That's good. Yes, I can imagine how hard it is to design such articles. Especially when you involuntarily limit yourself in some global refactoring by uploading codes to a resource.

What is this restriction expressed in what way?

Refactoring is performed, but it is a gradual process here. It is not possible to find the optimal version of this or that algorithm at once. The scheme is also gradually adjusted. As soon as you come up with an idea of how and what can be improved, changes are made immediately.

 
Hi, I am realy grateful for Your work, thank You.
I have problem with ColorPicker in new Builds. Does it work well in TestLibrary04 example?
I am using Your library compiled in MQL4. All old examples from previous version work well (after modifications), except example with ColorPicker from Chapter 9/1.
In TestLibrary04 clicking ColorButton in Tab1 opens empty window (W_DIALOG type) without any object.
I know that You do not support MQL4 version, but I think that MQL4 is not a reason.
 
stt:
Hi, I am realy grateful for Your work, thank You.
I have problem with ColorPicker in new Builds. Does it work well in TestLibrary04 example?
I am using Your library compiled in MQL4. All old examples from previous version work well (after modifications), except example with ColorPicker from Chapter 9/1.
In TestLibrary04 clicking ColorButton in Tab1 opens empty window (W_DIALOG type) without any object.
I know that You do not support MQL4 version, but I think that MQL4 is not a reason.
Use MetaTrader 5. The MetaTrader 4 version is no longer supported and I can't give you any advice.
 
stt:
Hi, I am realy grateful for Your work, thank You.
I have problem with ColorPicker in new Builds. Does it work well in TestLibrary04 example?
I am using Your library compiled in MQL4. All old examples from previous version work well (after modifications), except example with ColorPicker from Chapter 9/1.
In TestLibrary04 clicking ColorButton in Tab1 opens empty window (W_DIALOG type) without any object.
I know that You do not support MQL4 version, but I think that MQL4 is not a reason.