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

 
ddiall :

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.

 
MQL_User #:

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.

I don't remember. And I haven't tried it. If I try it, I'll write you back. But I'm on holiday.
 

Ok.

In my opinion it is a necessary thing, considering the size of the library and how long it takes to compile.

 
MQL_User #:

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 during compilation. It would be faster
 
Artyom Trishkin #:
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...

 
MQL_User #:

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
 
Aliaksandr Hryshyn #:
There are dll analogues, see documentation
h ttps:// www.mql5.com/ru/docs/basis/function/export

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....

 
The work is not polished yet. There are issues with simultaneous creation of several pending requests for the same ticket as these requests do not always work out correctly. Currently, the logic works correctly only if there is one pending request for each position or order. After a pending request is activated, executed and removed, it is possible to create a new pending request for this position or order (if they are still active).
I plan to fix this issue gradually along with the further development of the library functionality as soon as I already have some graphical library objects.

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

 
theonementor #:

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

No, unfortunately I haven't worked on this issue yet