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
It worked!!!
And here's how.
I installed a new MT5 in a clean field. The path to the MovingAverageWithFrames Expert Advisor was as follows: %MQL5\Experts\MacdSampleWithFrames\MovingAverageWithFrames.mq5.
It turned out that the robot did not work correctly in the first MT5, because the source was originally located here: %MQL5\Shared Projects\Testing\Frames\MovingAverageWithFrames\MovingAverageWithFrames.m q5.
Apparently, resources are connected from the shared projects folder problematically, if at all.
Give a complete layout of the files - what and where you have located relative to the MQL5 folder. It is possible that you have done something wrong.
Look through the thread starting from this post - https://www.mql5.com/ru/forum/224453/page6#comment_6359959.
The working version of the Expert Advisor, which renders everything normally, is located in the %MQL5\Experts\MacdSampleWithFrames folder.
The library is located in the folder %MQL5\Include\EasyAndFastGUI.
The pictures are here:
Now, the version of the Expert Advisor that does not render the panel normally is located here:
%MQL5\Shared Projects\Testing\Frames\MacdSampleWithFrames.
I don't understand why the resources are not loaded in the second version of the EA, which is in the shared folder? After all, the same headers are used, e.g.
%MQL5\Include\EasyAndFastGUI\Controls\Window.mqh.
Roche, I read the thread, but I didn't find an answer to my question there. If something is wrong, I apologise, after all Shared Projects is a new tool in the folder hierarchy. I haven't figured it out yet.
Forum on trading, automated trading systems and testing trading strategies
Discussion of the article "Visualise trading strategy optimization in MetaTrader 5"
Anatoli Kazharski, 2018.03.01 08:00
Such nuances should be reported immediately. In the archive attached to the article, the files are located in the MQL5/Experts directory instead of the Shared Projects directory. That's how you should have tested them first before trying something else.
So it seems that yes, you are right:
Обсуждение статьи "Визуализируем оптимизацию торговой стратегии в MetaTrader 5"
Dennis Kirichenko, 2018.02.25 22:10
I'm kind of not a newbie. Tried it from here. Nothing worked. Gave up, went about my business. Realised that it is extremely inconvenient to work with this library. A lot of versions, you can easily get confused...
Maybe my hands are crooked, I'm going to sprinkle them with holy water and see if it helps....
Anatoly, thank you for your work. Yes, it's my fault, I didn't realise at once where the problem came from.... Anyway, I would like to note that in your library, imho, you should specify the version in each header. Otherwise it's easy to mix them up, forget or not update them.... Holy water helps, I recommend it :-))))
I don't understand why resources are not loaded in the second version of the EA, which is in the shared folder? After all, the same headers are used, for example
%MQL5\Include\EasyAndFastGUI\Controls\Window.mqh.
Roche, I read the thread, but I didn't find an answer to my question there. If something is wrong, I apologise, after all Shared Projects is a new tool in the folder hierarchy. I haven't figured it out yet.
You need to enter all necessary files in the project itself and specify links to them. Try
Forum on trading, automated trading systems and testing trading strategies.
New version of MetaTrader 5 build 1745
Renat Fatkhullin, 2018.01.23 09:17
Only by the method of working in Shared Projects and the presence of a file exactly in the project folder inside Shared Projects.
This is the essence of collaboration - you make a physically alienated project and work with other participants in versioned catalogue replication mode. If you rely on non-standard (all but the standard MQL5 delivery) links outside the replicated catalogue, then you are doing it wrong.
The issue of duplicates is exclusively your personal problem. It cannot be solved by any magic. Your personal files will not be magically attached to someone else's replicated catalogue.
To make it quite clear:
The logic of working with shared projects is common. It has requirements and constraints without which everything falls apart. The approach "everything is wrong, I want it differently, I want it my way, I don't like it" won't work here - everything has been justified and correct for a long time.
So you have to adjust to these rules in order to get the right system of work.
... Still, I'd like to point out that in your library, imho, you should specify the version in each header. ....
If there will be more updates, I will do so. The version will be marked in the WndContainer.mqh file and in the library description in CodeBase.
In the project itself, you need to create all the necessary files and specify links to them. Try it
I did it! It turns out to be very easy and convenient. Here's how. I created a project: %MQL5\Shared Projects\MacdSampleWithFrames\MacdSampleWithFrames.mqproj.
I plugged only Sources and Headers into it by physically copying the example files into the project folder (highlighted by the red rectangle). And everything else (Dependencies and Resources) appeared in the folder hierarchy by itself. It's a handy thing. But as far as I understand, for this project to be 100% shared, all files must be physically moved to the project folder.
The Expert Advisor works, the Panel is rendered.
I try to run an example with MACD, I put all files and libraries in folders, as Dennis Kirichenko indicated above, I select the compiled Expert Advisor, in the tab of tester parameters I select Trailing optimisation from 30 to 100 with step 1. I press the Start button, at the end of testing I get the result as with a specific value.
I have not managed to get a beautiful picture with a fan of graphs.
Maybe someone has a video, how to start it all and how it works!?
...
Try this:
Trailing Stop Level > Start: 1, Step: 1, Stop: 100