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 burden is placed on the computer by the developer's negligent attitude towards the coherence of their mechanism. A desire to save energy on improving the system. Unreasonable consumption of computer resources in the name of making their work easier.
As long as the computer successfully copes with inefficiently written code, the developer will continue to "parasitize" on the processing power. This is a dead-end road.
Sooner or later, the ineffective mechanism will stop developing and be replaced by a better counterpart.
Man's time and effort will be wasted and his brainchild will end up in the dustbin.
In the competitive world, this risk exists all the time.
Designing mechanisms, we should think about their performance in the first place, and about the comfort and convenience of spending our working hours in the second.)
You still haven't written a function to define a new bar in procedural style.
Forum on trading, automated trading systems and testing trading strategies
Mt4 End of support.
Artyom Trishkin, 2017.09.10 23:21
I had a goal for the end result of his procedural style code to work in such a loop:
Yes, we discussed this yesterday.
I used to deal with another platform and there the bars were formed by time, regardless of quotes coming in (look in TWS).
I was told that this is not the case on MT.
I will add a quote arrival check to confirm a new bar occurrence event.
Been looking at it for a while now. Interesting platform, but as I understand it's not free, and if you're not sure you'll make money, it's a shame to pay to use the toy...
Apparently my experiment with trying to explain the self-taught point of view failed...
Is there, in principle, an example of this? Even if not yours? I have deep doubts. In early 2000's I stopped counting the number of debugged and working lines of code I wrote because it exceeded a million, it became uninteresting .
An elementary example would be to add another n-series of inputs to the EA, with different input parameters.
And, of course, maintaining these n-positions, with separate parameters, until closing.
...And most likely ( using oop) lines of code, you would have fewer. Although, there are adept at bloating the oop code)
I don't know if anyone has suggested it, but why not move everything in MT4 to MT5, then everyone would move.
And who would transfer this mountain of accumulated EAs, indicators and scripts?
I think I've found a primitive example of the usability of OOP. Here's a function for filling an array with a specified value. There are eight varieties, depending on the type of array.
Imagine you need to write a function that needs to pass one set of parameters, then another, then a third... Using algorithmic approach you'll get N different function's names. It would seem that there is nothing wrong, you can write 8 such functions as ArrayInitializeInt()ArrayInitializeDouble() and so on. But it's nice not to think about the type of array, just use one function in any case, and how safe it is to mix up which array you put there...
Developed a new solution for the new bar function. It is simpler and more concise. It has the possibility to receive notification about the new bar event on any of the symbols that are available in the market overview and on any of the preset timeframes.
If you see any errors, please comment.
Developed a new solution for the new bar function. It is simpler and more concise. It has the possibility to receive notification about the new bar event on any of the symbols that are available in the market overview and on any of the preset timeframes.
If you see any errors, please comment.
4 cycles isn't it cool ? at 600 symbols in market overview every minute the terminal will die ....
Developed a new solution for the new bar function. It is simpler and more concise. It has the possibility to receive notification about the new bar event on any of the symbols that are available in the market overview and on any of the preset timeframes.
If you see any errors, please comment.
I don't expect this function to jump into OnTimer() and I have already commented on my idea
Forum on trading, automated trading systems and strategy testing
Mt4 End Support.
Alexey Viktorov, 2017.09.11 10:09
Apparently my experiment with trying to explain a self-taught point of view failed...
Developed a new solution for the new bar function. It is simpler and more concise. It has the possibility to receive notification about the new bar event on any of the symbols that are available in the market overview and on any of the preset timeframes.
If you see any errors, please comment.
As for comments on the code: What if you need to define the opening of the current period and only one symbol in the program? The whole structure will loop all the loops? It's not rational.
ps; And why should I start a millisecond timer? Isn't a second timer enough?