![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
I am preparing an update and there will be no lesson today. Those interested in the material can take a day or two off. :)
We will continue on the new build of the builder.
A big request to people who are trying to create the interface or testing the constructor. Please report all the bugs you find. Feedback from you is very important. Thanks in advance.
I've been pondering whether I should, or wait until I find out.....
Well, here it is then. I don't know if it's a bug or if I wrote the code wrong.
Some rubbish fills the table's free space on V_BOX.
Also, on H_TAB, "Report", until I added the icon, there was some ghost of an icon distorting the title. It was disappearing after clicking on it.
I don't know if it's a bug, but the described TEXT_ALIGN_*s are missing.
There are still many questions about implementation, I'm still figuring it out on my own. I think we should wait for you to get to these topics. Unless you think otherwise.
I was contemplating whether I should, or wait until I find out.....
Well, here we go. I don't know if it's a bug or if I wrote the code wrong.
Some rubbish fills the table's free space on V_BOX.
Also, on H_TAB, "Report", until I added the icon, there was some ghost of an icon distorting the title. It was disappearing after clicking on it.
I don't know if it's a bug, but the described TEXT_ALIGN_*s are missing.
There are still many questions about implementation, I'm still figuring it out on my own. I think we should wait for you to get to these topics. Unless you think otherwise.
Thanks for the feedback.
On the code:
1. V-box(es) and tabs are always written in separate groups. It is more convenient. It is desirable not to add anything else to these groups. Otherwise, the"positioning jungle" begins. Of course you can do it this way, but it is not worth it....
2. The enumeration is not finished. There is no k.word END in this line.
('Quite a rude error for a constructor. It may glitch a lot.)
3. In the tables you put the word 'TEXT'. This is unnecessary. CELL cells have their own parameter that gets a value from the user application when connected. Or, use the word V_CURRENT to set the value .
For example:
CELL, A, V_CURRENT, 123,
And cells of type "T_CELL" are used to display unchanging text in tables. They pass the name text to the table. For example:
4. Try to remove the word TEXT from the tables.
5. Let me know what you get. I will be glad to help you.
Question:
There is a catalogue "Include\(1) KIB 1.0\(1) BASE\(1) DOCUMENTATION\"
Are these just code samples, or is this intended to be compiled together as a demo programme? What is the correct way to use it?
Another important nuance. In the header of all tables the element T_HEADER is written:
Question:
There is a catalogue "Include\(1) KIB 1.0\(1) BASE\(1) DOCUMENTATION\".
Are these just code samples, or is this intended to be compiled together as a demo programme? What is the correct way to use it?
These are just examples of different codes written at different times and at different stages of the designer's evolution. Some of them may no longer be relevant, some of them may not work, some of them may not need to be written at all, and some of them may be quite suitable. It's hard to say...
In the next build I will clean this code base and leave only working variants.
Very important nuance. Tabs control the switching of V_BOX(a) canvas images. They must be declared above. Tabs first, then V_BOX(es ).
Question:
There is a catalogue "Include\(1) KIB 1.0\(1) BASE\(1) DOCUMENTATION\".
Are these just code samples, or is this intended to be compiled together as a demo programme? What is the correct way to use it?
The most working codes are in the folder "Include\(1) KIB 1.0\(1) BASE\(2) STATE KIB-CODE"
There are codes of windows of the designer. You can study them.