Well, yes, a weightless indicator for each desired chart via a template, and EventChartCustom in one EA. If for yourself, it's a good solution, better than cycles.
Shove the code that Alexey gave you into the Timer with an interval of a couple of seconds. Also add a line that if market is closed- exit, so as not to run the cycle.
This approach will relieve CPU load in fast market, and in slow market it will allow to track object appearance on another chart faster.
Aleksei Stepanenko: Well yes, a weightless indicator on each desired chart via a template. If for yourself it's a good solution, better than cycles.
The advantage of this approach is that when an object appears the event is sent 1 time instantly, this simplifies EA development, but complicates indicator development, although the end result is worth the effort.
Well on any one chart 1 EA is listening, with event handling and trading logic.
I have one trading panel implemented this way: 1 EA, and an indicator with buttons on different charts, the bunch works great and does not consume memory
I have EAs on the charts, and opening additional copies of windows to trade from the panel is not the right thing to do. That's why the trading panel was written in the form of an indicator - you can put a lot of them on one chart.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Shove the code that Alexey gave you into the Timer with an interval of a couple of seconds. Also add a line that if market is closed- exit, so as not to run the cycle.
This approach will relieve CPU load in fast market, and in slow market it will allow to track object appearance on another chart faster.
Well yes, a weightless indicator on each desired chart via a template. If for yourself it's a good solution, better than cycles.
The advantage of this approach is that when an object appears the event is sent 1 time instantly, this simplifies EA development, but complicates indicator development, although the end result is worth the effort.
Well on any one chart 1 EA is listening, with event handling and trading logic.
I have one trading panel implemented this way: 1 EA, and an indicator with buttons on different charts, the bunch works great and does not consume memory
And again an indicator on every chart?
the indicator gets from all the right charts, but the robot is hovering on one chart
the indicator gets from all the right charts, but the robot is hovering on one chart
Yes, Vitaly, that's right! Saving resources - our everything ;)
Well, I have a different goal than saving money.
I have EAs on the charts, and opening additional copies of windows to trade from the panel is not the right thing to do. That's why the trading panel was written in the form of an indicator - you can put a lot of them on one chart.
Well, I had another purpose besides saving money.
Interesting
i'm sorry to interruptthe conversation, can someone pleaserespond to my post above????
Where is the indicator? Please attach it here so you don't have to wander around the forum threads.