Discussion of article "Library for easy and quick development of MetaTrader programs (part XXXIV): Pending trading requests - removing and modifying orders and positions under certain conditions" - 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
Hello Artyom, I remember you mentioning this future graphical shell the first time I read these articles some weeks ago... Can you provide more details about your vision for this and what it will allow us to do in practice?
Ohoh ... Too broad a topic to tell in a nutshell like this ...
Almost every object will have its own graphic object, which allows displaying all its information about its "parent". Each object will be accessed from other objects - just like we now have access to different objects. All graphic objects will be able to interact with other objects. Each object will have its own type of graphical representation. There will be many types of graphic objects from which you can compose your own complex graphic objects. Each object will have the ability to interact with the mouse cursor and, accordingly, different reactions and handlers. As a result, it will be possible to create your own types of graphical representations for various objects and how they interact.
Artyom.
Is there any possibility to connect this library to the Expert Advisor in compiled form? So that in case of small changes in the Expert Advisor it would not be necessary to compile the whole library every time.
I think there should be such a possibility, but I can't figure out how to do it.
Artyom.
Is there any possibility to connect this library to the Expert Advisor in compiled form? So that in case of small changes in the Expert Advisor it would not be necessary to compile the whole library every time.
I think there should be such a possibility, but I can't figure out how to do it.
Ok.
In my opinion it is a necessary thing, considering the size of the library and how long it takes to compile.
Okay.
In my opinion, it is a necessary thing, considering the size of the library and how long it takes to compile.
You can disable optimisation at compile time. It will be faster
Yes, it will indeed be faster. But only twice as fast.
On my laptop the compilation time was up to 60 seconds, now, after disabling optimisation, it comes down to 30 seconds. And if we take into account that this is only the 34th part (not the last one), it's still a lot. After all, the library will only grow further....
I thought that it could be easily made as a DLL (for example) and connected to the Expert Advisor. But I tried, and... it's not quite clear how to do it...
I thought that it could be easily made as a DLL (for example) and connected to the Expert Advisor. But I tried, and... it's not quite clear how to do it...
There are dll analogues, see documentation
Thanks.
That seems to be exactly what I need. At least theoretically. But in practice, when I try to compile the Engine file with #property library, I can' t export methods (which are essentially functions) - I get an error. It looks like we need to add more functions (exportable) that call these methods. Besides, there will be no tooltips in the programme that imports these functions.
In general, all this is not quite as I would like it to be....
Did you ever polish and fix this issue in future chapters or did you forgot about this when you developed the graphical section? If you fixed and polished can you tell me in which chapter it is?
Thanks
Did you ever polish and fix this issue in future chapters or did you forgot about this when you developed the graphical section? If you fixed and polished can you tell me in which chapter it is?
Thanks