Thanks to the author for the quality work.
Waiting for the video.
And more realisation of window dynamism. If possible).
In my opinion, this would be a logical conclusion of the whole work, and would make the interface written with the help of the provided library completely complete.
(This proposal is an expression of desire of "interested user". Nothing more.)
There are 3 radio buttons on the Tab 1 tab, what and where should I add in this example so that when switching them just pops up an alert with the name of the pressed button?
p.s. In this example, in the MainWindow.mqh file in the bool CProgram::CreateTable function there are two defines: COLUMNS2_TOTAL and ROWS2_TOTAL, and then in the same function the defines COLUMNS1_TOTAL and ROWS1_TOTAL are used. This is probably an error.
There are 3 radio buttons on the Tab 1 tab, what and where should I add in this example so that when switching them just pops up an alert with the name of the pressed button?
In the event handler of the custom class CProgram::OnEvent() add this block of code:
//+------------------------------------------------------------------+ //| Graph event handler| //+------------------------------------------------------------------+ void CProgram::OnEvent(const int id,const long &lparam,const double &dparam,const string &sparam) { //... //--- Click event on the text label if(id==CHARTEVENT_CUSTOM+ON_CLICK_LABEL) { //--- If you pressed the radio button if(lparam==m_radio_buttons1.Id()) { ::Alert("element id (lparam): ",lparam,"; radio button index (dparam): ",(int)dparam,"; radio button description (sparam): ",sparam); return; } //--- return; } //... }
//---
Result:
//---
p.s. In this example, in the MainWindow.mqh file in the bool function CProgram::CreateTable there are two defines: COLUMNS2_TOTAL and ROWS2_TOTAL, and then in the same function the defines COLUMNS1_TOTAL and ROWS1_TOTAL are used. This is probably an error.
Yes. I was transferring the code from another file and forgot to fix it.
Waiting for the video.
And more realisation of window dynamism. If possible).
In my opinion, this would be a logical conclusion of the whole work, and would make the interface written with the help of the provided library completely complete.
(This proposal is an expression of desire of "interested user". Nothing more.)
There's a lot more to do before it's fully functional and the logical conclusion of the whole work, besides window dynamism. There will be at least nine more controls. And also we need to make some improvements that will simplify the creation of the interface, as some users have difficulties. And it would not hurt to make help documentation too. To be more precise, it is even necessary, but I will do it only after the development is fully completed. This is still a long way off.
Before a completely complete state and logical completion of the whole work, there is a lot more to be done besides window dynamism. There will be at least nine more controls. And we also need to make some improvements that will simplify the creation of the interface, as some users had difficulties. And it would not hurt to make help documentation too. To be more precise, it is even necessary, but I will do it only after the development is fully completed. That's not for a while.
I see.
Window dynamism is not the main thing. But it's convenient.
Very interesting, what other controls you are going to add.
Will you make a video with demonstration of the interface features?
Or, for example, you could film the process of creating an interface for a small expert working on MA.
I would really like to see the final result in action.
I would check everything myself, but frankly speaking I have absolutely no time as I am very busy with my work.
Besides, such a video could attract a lot of attention from users.
I see.
Window dynamism is not the main thing. But it is convenient.
Very interesting, what other controls are you going to add.
Will you make a video with demonstration of the interface features?
Or, for example, you could film the process of creating an interface for a small expert working on MA.
I would really like to see the final result in action.
I would check everything myself, but frankly speaking I have absolutely no time as I am very busy with my work.
Besides, such a video could attract a lot of attention from users.
All this and much more has been planned already too. There will be a lot of working examples that will help MQL-developers to use this library in their projects. Unfortunately, I can't devote much time to each of them individually. But I can find time for articles.
From the elements will be, for example:
- Element "Time".
- Element "Text field" with automatic word transfer + scroll bar.
- Lists of radio buttons and check-boxes with a vertical scroll bar.
- And much more.
Thank you. That's what I did, but I didn't put :: in front of Alert so it didn't work.
The absence of :: shouldn't have had any effect. The error was something else.
Maybe I deleted my code and now I can't say for sure.
The error occurs when I close the window created by the indicator with a cross. I slightly changed the MainWindow.mqh file from the example located here: Indicators\Article 10\SeparateWindow.
and I don't understand how to delete a row in the created table ?

- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
New article Graphical Interfaces X: Updates for Easy And Fast Library (Build 2) has been published:
Author: Anatoli Kazharski