Discussion of article "Graphical Interfaces II: the Menu Item Element (Chapter 1)"
For the rest of us the usefulness and necessity is not quite clear. So please ask the author. Could you make a video of the most tricked-out (taking into account all future articles on the topic) graphical interface, showing all the features there?
Since hardly anyone will read and understand such extensive material without understanding why it is necessary. And on video-demonstration everyone will decide for himself whether he needs it or not. And even if they don't need it now, they will get an idea of the possibilities that can be emphasised in the future. And if, indeed, interested, they will read the articles carefully and ask questions on the matter.
Please on behalf of NOT freelancers and sellers.
For freelancers and sellers (Market) the creation of a graphical interface is of great importance, as it allows to attract potential customers/buyers.
For the rest of us the usefulness and necessity is not quite clear. So please ask the author. Could you make a video of the most tricked-out (taking into account all future articles on the topic) graphical interface, showing all the features there?
Since hardly anyone will read and understand such extensive material without understanding why it is necessary. And on video-demonstration everyone will decide for himself whether he needs it or not. And even if they don't need it now, they will get an idea of the possibilities that can be emphasised in the future. And if they are really interested, they will read the articles carefully and ask questions on the matter.
Please on behalf of NOT freelancers and sellers.
For those who are learning MQL and object-oriented programming, I think it will be interesting to read. It is much easier to learn a programming language on such projects, rather than on some abstract examples, which really very often do not answer the question: "And where can this be applied?".
I, for example, really needed such a library, but from what was offered to the MQL community, I lacked a lot of things for comfortable use.
I won't make a video yet, and there is still a lot of work to do without it. Besides, a graphical interface without content, no matter how fancy it is, has no sense, i.e. it will not answer your question at all. Everyone has to come up with an idea why he needs it. And if there are no ideas, then it turns out that it is not necessary.
Let's say you have some idea for developing a complex trading strategy. Let it be several trading strategies. It is convenient to create a graphical interface to manage them. Or let it be your own tester, which is better than the standard one in your opinion. Or your programme needs to specify some data from the terminal's file sandbox, but not by entering a string containing the full path to the file, but through a file navigator, which can be created with the help of this library easily and simply. Perhaps it is some kind of analytical program for conducting researches or calculations with data visualisation immediately on a graph in the terminal. Build your own charts that are not bound to the time scale of the chart where the programme is located. A graphical interface is needed to manage all this "orchestra" conveniently. After all, sometimes you may need to change values of some parameters on the fly, switch to some other mode, open and visualise some data. And instead of constantly going into the code or external parameters of the programme, which in my opinion is very inconvenient, if the application is a whole complex, you can simply create a compact graphical interface.
During real-time trading I want to see how trading would be in the tester - real-time. I.e. I see the combat environment by normal means. And I can see the tester real-time environment using your visualisation tools. At the same time, I can see the history in this virtual tester and the trades chart.
This will allow you to quickly analyse the reasons of discrepancies between the tester and the real one: requotes, re-jacks and other nuances. Is your library able to easily create an interface like on the picture in this article?
Will the library draw 2D charts?
zaskok3:
Yes, but if you write such a tester yourself. And with the help of this library you can create a graphical interface for it.
zaskok3:
This will allow you to quickly analyse the reasons for the divergence between the tester and the real: requotes, re-jacks and other nuances. Is your library able to easily create an interface like on the picture in this article?Yes, it can. But we will have to wait until the whole library is published. There will be about 20 articles in total, maybe even more. At the moment only 6 articles of the series have been published so far.
zaskok3:
2D charts will be drawn by the library?
I already have one such class-element and it may well be enough for you. But it is only a slightly modified class from the standard library. Of course, it is not enough for me too and I plan to create my own library for drawing charts. Unless someone writes it before me. ) I would like something similar to such a quality as it is implemented, for example, in Excel.
Please add links to the list of articles in Part 2:
Список статей (глав) второй части: Графические интерфейсы II: Элемент "Menu item." (Глава 1) Графические интерфейсы II: Элементы "Dividing Line." и "Context menu." (Глава 2) Графические интерфейсы II: Настройка обработчиков событий библиотеки (Глава 3) Графические интерфейсы II: Элемент "Main Menu." (Глава 4)
Right now only the first one (Chapter 1) is clickable. Similarly, I would like to see all the links at the end of chapters 2 and 3.
- 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 II: the Menu Item Element (Chapter 1) has been published:
In the second part of the series, we will show in detail the development of such interface elements as main menu and context menu. We will also mention drawing elements and create a special class for it. We will discuss in depth such question as managing program events including custom ones.
In the chapters of the first series, we discussed in full the process of developing the main structure of the library for creating graphical interfaces. There, we also created the main element of the interface - a form for controls. The first article: Graphical Interfaces I: Preparation of the Library Structure (Chapter 1) explains in detail what this library is for. A complete list of links to the articles of the first part is at the end of each chapter. There, you can also download a complete version of the library at the current stage of development. The files must be placed in the same directories as they are located in the archive.
The Main Menu of the Program
It is difficult to find a program that does not have the main menu. The MetaTrader terminals also have this interface element (see the screenshot below). Usually, the menu is located in the top left part of the program window and consists of several items. A left mouse click on a menu item brings up a drop-down list with the program options.
Fig. 1. Main menu in the MetaTrader 5 terminal
This drop-down list is called a context menu and can contain several types of items. Let us consider each of them in detail:
Author: Anatoli Kazharski