Discussion of article "Graphical Interfaces VIII: the File Navigator Control (Chapter 3)" - page 3
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
You need to use CFileNavigator::TreeViewAreaWidth() and CFileNavigator::ContentAreaWidth() methods to specify the width for the tree list area and the content area. If you don't set the width of the content area, the right edge of the navigator will automatically be aligned to the right edge of the window.
Volume VIII (8), Chapter 3... how much is in there? ...is horrifying.
Anatoly, you may be criticised for narrow specialization, but you have my deepest respect and esteem!
If there is similar material in other areas, the MQL-community will only benefit. You may see your own MQL-Boost :-))).
Anatoly, you may be criticised for narrow specialization, but you have my deepest respect and esteem!
If there is similar material in other areas, the MQL-community will only benefit. You may see your own MQL-Boost :-))).
I like criticism. You can learn a lot of new things through it. )
What is MQL-Boost ?
P.S. It looks something like this: Boost >>>. Yes, everything naturally goes to that. )
Interesting dreams. However, there is a variant when creating graphical interfaces of user applications will not require using any code libraries at all (well, unless developers just want to complicate their work).
What is it about the option to make something out of nothing that is so interesting? )
You know, it's not very pleasant to play the role of a person who can make someone else's titanic labour meaningless with a few phrases. But, since you don't see an alternative way of creating and working of the user interface, I'll show it to you. The essence is as follows: there is a graphical engine working with windows and controls. The controls are represented by strings of data written in the kernel. The kernel is easily constructed with the help of special tables directly in a text file. After compilation the kernel is loaded into the engine. The engine is implemented as an indicator. Weighs no more than 500 kb. Reproduces any standard interfeses prescribed in the kernel. Control elements through shared memory control the parameters of the user's application. If the MC provides shared, global memory in the form of a dynamic string array, the system will work fine. It will be possible to design the interface first in tables in files, then - in vis. studio.
You know, it's not very pleasant to play the role of a person who can make someone else's titanic labour meaningless with a few phrases. But, since you don't see an alternative way to create and work with the user interface, I'll show it to you. The essence is as follows: there is a graphical engine working with windows and controls. The controls are represented by strings of data written in the kernel. The kernel is easily constructed with the help of special tables directly in a text file. After compilation the kernel is loaded into the engine. The engine is implemented as an indicator. Weighs no more than 500 kb. Reproduces any standard interfeses prescribed in the kernel. Control elements through shared memory control the parameters of the user's application. If the MC provides shared, global memory in the form of a dynamic string array, the system will work fine. You will be able to design the interface first in tables in files, then - in vis. studio.
Ah, you're still talking about the same thing. I remember that, I thought you had invented something new. Then I'm waiting for your implementation for tests.
But no matter what your result will be, I will continue to develop my project, because your alternative, at least for me, is not suitable for my projects. I need a fully manageable and available for study (with source codes) project that I can develop further on my own.
Perhaps your alternative will suit someone better.
Oh, you're still talking about the same thing. I remember that, I thought you'd come up with something new. Then I'm waiting for your implementation for tests.
But regardless of what your result will be, I will continue to develop my project, because your alternative, at least for me, is not suitable for my projects. I need a fully manageable and available for study (with source codes) project, which I can develop further on my own.
Perhaps your alternative will suit someone better.
Logic tells me that these two options are mutually exclusive. If it is not so, I will be only glad. I'm working on finishing the project. How long it will take I can't guess, but the project will be finished. Perhaps in the future we will even co-operate with you).