Discussion of article "Library for easy and quick development of MetaTrader programs (part XVII): Interactivity of library objects" - 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
The philosophy here is this: induction (from the particular to the general) or deduction (from the general to the particular).
Artyom uses the inductive method of presenting the material.
Chief: Well, Gleb Georgievich, there's a bullet. Your judgement...
Zheglov: Well, what do you think, "intelligence"?
Sharapov: Well, the bullet is like a bullet, ordinary, pistol bullet....
Zheglov: Yes, it would be good to find a casing.
Chief: It's better to look at the weapon itself.
Zheglov: That's right. Well, it means this: a bullet fired from an imported weapon of 6.35 calibre of the Bayard or, say, Omega system.
Chief: What does that mean?
Zheglov: The bullet, Sergei Ipatich, the bullet. Six left verical rifling cuts, that's it - the handwriting is quite "independent".
Chief: What do you say to that? Judging by the markings, the cartridge case is ours, domestic.
Zheglov: Yes. Where was it found?
Chief: Where it should be. To the left of the body. The reflector worked properly.
Zheglov: Yes, the casing is ours. Hmm. Well, we'll put it in the riddle. We still have to look for the weapon. Nadezhda, do you know if there were any weapons in the house?
Nadezhda: I don't know.
[Weiners. The Age of Mercy]
Oh, how... I didn't know it was like that.
I read Vainers as a child.
New article Library for easy and quick development of MetaTrader programs (part XVII): Interactivity of library objects has been published:
Author: Artyom Trishkin
Thank You for all the work You put in to those articles. I can learn a lot from them :)
Thank You for all the work You put in to those articles. I can learn a lot from them :)
Hello - I very much like the potential of the event-driven capability you implemented in CSymbol, such as SetControlBidDec, SetControlAskLevel, etc... I haven`t studied your later articles on indicators yet (after part 38), but would like to understand if you intend to add the ability to set similar events on indicators (e.g. price touching/crossing a certain moving average value, etc)?
What is your recommended approach to implement such checks in the current version of the library? Is there an alternative to checking every time in OnTick()? What about if I'm working with multiple symbols?
Hello - I very much like the potential of the event-driven capability you implemented in CSymbol, such as SetControlBidDec, SetControlAskLevel, etc... I haven`t studied your later articles on indicators yet (after part 38), but would like to understand if you intend to add the ability to set similar events on indicators (e.g. price touching/crossing a certain moving average value, etc)?
What is your recommended approach to implement such checks in the current version of the library? Is there an alternative to checking every time in OnTick()? What about if I'm working with multiple symbols?
Hi. I have not thought about implementing the same event model for indicators yet. I am not very happy with the implementation of indicators. Therefore, I will add indicator objects, and they will already refer to the required bars in the timeseries for the required indicator data. And there, the implementation of the event model will already be easier.
Hi. I have not thought about implementing the same event model for indicators yet. I am not very happy with the implementation of indicators. Therefore, I will add indicator objects, and they will already refer to the required bars in the timeseries for the required indicator data. And there, the implementation of the event model will already be easier.
Is the main purpose of your indicators support in DoEasy to help the library user to implement their own indicators? Do you also plan to allow multi-platform access to any indicator data in MT4/MT5 from other programs, for example EAs? As you know, currently functions such as iMACD(), iBands(), etc work very differently between MQL4 and MQL5 so I want to write some wrapper functions to enable my EAs coded with DoEasy can run on both versions.
Is the main purpose of your indicators support in DoEasy to help the library user to implement their own indicators? Do you also plan to allow multi-platform access to any indicator data in MT4/MT5 from other programs, for example EAs? As you know, currently functions such as iMACD(), iBands(), etc work very differently between MQL4 and MQL5 so I want to write some wrapper functions to enable my EAs coded with DoEasy can run on both versions.
Yes. I have already started writing an article about indicator objects. It is with their help that everything will be simple and, I hope, the way most users of the library will be satisfied.