Discussion of article "Visualizing trading strategy optimization in MetaTrader 5" - page 4
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 can't help you in this case.
A simple script from your side would probably help to localise the problem.
Or better yet, we could Skype together in the screen demo mode and quickly solve everything. The result - here.
...
In your code samples to the article, in the downloaded files, the MacdSampleWithFrames.mq5 file is identical to the MovingAverageWithFrames.mq5 file in terms of code content.
...
This is how it should be. The difference is in other files.
Tested on another terminal, where all files are stored in the folder %AppData\Roaming\MetaQuotes\Terminal\.....
Same error. Something is wrong somewhere...
I'll try to find out the cause of the problem later.
I have all terminals in /portable mode
Look, so will the timer work in your panel or not?
Look, so will the timer work in your panel or not?
Thanks for the suggestion, but having looked at the code, I didn't feel like testing this.
I believe that to start the timer after frame-mode optimisation there should be nothing but this:
void OnTesterDeinit() { EventSetTimer(1); } // Set a timer at the end of OptimisationI consider the lack of this feature to be a bug. I haven't written to servicedesk yet.
I consider the lack of this feature to be a bug. I haven't written to Service Desk yet.
Until they eliminate the Frame vulnerability, it is very dangerous to enable OnTimer.
It is very dangerous to include OnTimer until they eliminate the Frame vulnerability.
So we should wait until this vulnerability is eliminated.
What did Service Desk tell you about this?
So we'll have to wait for the vulnerability to be fixed.
What did Service Desk tell you?
They didn't say anything. I think it won't be possible to eliminate the vulnerability, because they will need to close a lot of holes, thus negating all the advantages. It's good that OnDeinit doesn't work now.
No response. I think it won't be possible to eliminate the vulnerability, because it will take a lot of holes to close, negating all the advantages. It's good that OnDeinit doesn't work now.
Of course, you can think whatever you want. But it's better to wait for an official answer.
It was announced that work on updates for the tester is in progress. There are a lot of items that need to be implemented. They will do it, they will answer those requests that are unanswered now.
In principle, what you called a vulnerability is not a vulnerability. It can be easily checked and excluded by current means. That's why you can include a timer and generate the OnDeinit event.
In principle, what you called a vulnerability is not a vulnerability. It is easy to check and exclude it with current tools. That's why you can include a timer and generate OnDeinit event.
This is a Market vulnerability in the first place.