
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
Re-read with interest, hmmm.
These all dances with tambourine would not be necessary!!! if!!! MQs would switch on!!! the broadcasting of the glass on the DC server by default, and would not allow DCs to switch them off. Let it be an empty bet with only bid and ask, but it should be broadcasted.
Then a multicurrency tick can be easily tracked in OnBookEvent by subscribing to the required instrument.
In fact, OnBookEvent is a standard multicurrency tick handler.
And so far it is possible only in dillings that translate the glass.
The code from the article is outdated.
Yes, the code was written when OnChartEvent handler didn't work in the tester yet.
Re-read with interest, hmmm.
These all tambourine dances would not be necessary!!! if!!! MQs would enable!!! beaker broadcasting on the DC server by default, and would not let DCs switch them off. Let it be an empty bet with only bid and ask, but it should be broadcasted.
Then a multicurrency tick can be easily tracked in OnBookEvent by subscribing to the required instrument.
In fact, OnBookEvent is a standard multicurrency tick handler.
And so far it is possible only in dillings that translate the glass.
I played with OnBookEvent once. For experts, in general, it would work. Although I would remove "broadcasting" and make a subscription for charts. Another minus: it doesn't work in indicators. I haven't tried it in the tester.
Since the first publications on this topic a lot of tambourines have been killed. Something more acceptable has appeared. Maybe I will publish it sometime.
Yes, the code was written when the OnChartEvent handler didn't work in the tester yet.
I was playing with OnBookEvent. For experts, in general, it would be fine. Although I would remove "broadcasting" and make a subscription for charts. Another minus: it doesn't work in indicators. I haven't tried it in the tester.
Since the first publications on this topic a lot of tambourines have been killed. Something more acceptable has appeared. Maybe I will publish it sometime.
There is a more subtle way of doing it, there is a subscription not for charts, but for specific Expert Advisors.
So you will not receive the signals of the chart without subscription. Therefore, the broadcasting is quite qualitatively processed.
Run owls in the attachment on two charts that have a stack. Each owl will receive only the signal to which it is subscribed.
Hi Lizar,
I want to use your code, but my broker using mql4 language (TradeMasterFX Meta, Version: 4.00 Build 890),
Is there a way to upgrade my terminal to mql5 supporting terminal?
Thanks for your advise,
Emre
Welcome to the discussion ;)
Forum on trading, automated trading systems and testing trading strategies
Features of mql5 language, subtleties and techniques of work
Andrey Khatimlianskii, 2018.10.09 23:18
When running an empty Expert Advisor using spy on 50 instruments, messages start pouring into the log:
If you add a filter to the indicator for the frequency of sending kastum events in 500 ms, the errors become less frequent, but do not disappear.
Is it just me?
EA code:
Profiler shows 95% of the time iCustom, OnChartEvent takes almost nothing. The processor (i5-3570) is loaded at 75%.
I invite discussion ;)
I have a suggestion to try to use IndicatorRelease() and IndicatorDelete () the appropriate number of times in OnDeinit() of your EA.
It should not come to OnDeinit, I need it all to work.
After deleting the EA everything is ok, memory is freed after some time.
It doesn't have to come down to OnDeinit, I need it all to work.
After deleting the Expert Advisor everything is ok, memory is freed after some time.
I suggest profiling the indicator to find out where exactly 4281 ms are wasted. Maybe in the message sending itself.
It is reasonable to profile the indicator to find out where exactly 4281 ms are wasted. Could be in the message sending itself.
We did it.
EventChartCustom at some point starts to run for more than 3 seconds.