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
Vomit, Edward, vomit =)
I understand that, but why couldn't it have been done in the way I described above?
It would have had no effect on the speed of processing the information:
If there was any information on the tool - record the date when it first appeared and store it in memory - 8 bytes!
You can even not store it, but when you do SymbolSelect(), you put it into memory.
When we address it with the SeriesInfoInteger (SERIES_TERMINAL_FIRSTDATE) function, we get:
A -1 - no data
Б. 0 - no data available but not ready
В. A - date of the first information
Then everything would be clear and transparent.
-1 - Going to the server
0 - We wait for the next iteration to check and/or build the timeseries
> 0 Build timeseries
From your reference I understood that YOU almost did that, turns out not.
Apparently one programmer started writing and someone else finished
Your implementation is good for FOREX, but very inconvenient for FORTS.
For FORTS, quotes may not come for a long time and the time series is downloaded from the platform.
and you have to repeat the whole process of data retrieval again, and with server login!
Use Expert Advisors to work with multiple symbol data, everything will be convenient and easy. The indicators in the MT5 environment are primarily designed to quickly calculate their time series data and display the results of the calculation on the chart. As the platform evolved, they gained many functions available to experts, but the basic architectural restrictions remained. And there is no reason to completely eliminate the differences between indicators and EAs. Once again I would like to remind you that the most important difference is that the Expert Advisors have their own processing flow. The indicators are calculated in a service flow, and this flow performs many other functions. This is why even the functionality we have in common with the Expert Advisors is implemented differently.
As for access to the history, there is no universal solution. The terminal cannot predict in advance what the user wants, i.e. whether the Expert Advisor wants to get only one date or wants to request the entire available history. The terminal chooses the fast access to the timeframe, i.e., at the user's request, it tries to cache the current (synchronized with the server) state of the history in full. Yes, there is a class of applications where this approach is not convenient. But if the programmer will not focus on the demand to rewrite the terminal "personally", he will find a solution in the existing functionality. If there is no solution at all, only then the question of extending the functionality arises.
Describe a specific problem with a specific code, without generalizations. Otherwise, you get an incomprehensible functionality of one single function bloated into "everything is wrong" and "everything is inconvenient".
Use Expert Advisors to work with multiple symbol data, everything will be convenient and simple. Indicators in the MT5 environment are primarily designed to quickly calculate on their time series data and display the results of the calculation on the chart. As the platform evolved, they gained many functions available to experts, but the basic architectural restrictions remained. And there is no reason to completely eliminate the differences between indicators and EAs. Once again I would like to remind you that the most important difference is that the Expert Advisors have their own processing flow. The indicators are calculated in a service flow, and this flow performs many other functions. That is why even the functionality shared with the Expert Advisors is implemented in different ways.
As for access to history, there is no universal solution. The terminal cannot predict in advance what the user wants, i.e. whether the Expert Advisor wants to get only one date or whether it wants to request the whole available history. The terminal has made a choice in favor of rapid access to the timeframe, i.e. at the user's request, it tries to cache the current (synchronized with the server) state of the history in its entirety. Yes, there is a class of applications where this approach is not convenient. But if the programmer will not focus on the demand to rewrite the terminal "personally", he will find a solution in the existing functionality. If there is no solution at all, only then the question of extending the functionality arises.
Describe a specific problem with a specific code, without generalizations. Otherwise, you get an incomprehensible functionality of one single function bloated into "everything is wrong" and "everything is inconvenient".
Hello, Anton!
Let us "break down" your answer:
1. "Use experts to work with multiple character data, everything will be convenient and simple."
I need a history (close) on 3 symbols with mapping to a chart.
Is there any other way to get close history from EA?
And I have to make a "vegetable garden" to draw results from an EA (in a separate window)!
2. "As for access to the history, there is no universal solution. The terminal cannot predict in advance what the user wants, i.e. whether the Expert Advisor wants to obtain only one date or wants to request the entire available history".
There is no need to predict the consumer's wishes. You just have to "tell" what state the data is in on the symbol AND ALL!!!
Then the user will know exactly what actions to perform next.
3."But if a programmer does not focus on the requirement to rewrite the terminal "personally", he will find a solution in the existing functionality.
I didn't say, much less demand to do something "for yourself", and the solution will of course always be found in the existing functionality.
4. "If there is no solution at all, that's when the question of extending the functionality comes up. "
You don't need to extend the functionality, you can just introduce minor changes for ease of use and speed.
5. "Describe a specific problem with a specific code, without generalisation.Otherwise, you get the misunderstood functionality of one single function bloated into "everything is wrong" and "everything is inconvenient""
OK, I'll prepare myself for an "extended" explanation of the problem with a specific code.
Only, unfortunately, you can't "rely" on the reference book...
Thanks for replying.
As always, the user position is that I am the centre of the universe and the world revolves around me. You have to use the functionality that is available. Especially since it has been shown more than once how to get the data.
As always, the user's position is that I am the centre of the universe and the world revolves around me. You have to use the functionality that you have. Moreover, it has been shown more than once how to get the data.
And you think it's the other way around. The centre of the universe is the developers and the world revolves around them? Is it so?
Then answer one question: Who is this terminal being developed for? Are they making it for themselves or for the user?
If they do it for themselves, no questions ... It's OK.
And if it's for the user, then their opinion should be listened to at least...
........
Describe a specific problem with specific code, without generalizations. Otherwise, it turns out that the misunderstood functionality of a single function is blown up to "everything is wrong" and "everything is inconvenient."
Describing:
Real account FORTS broker.
Problem - I'm not getting timeseries data.
1. The pictures show that there is data in the terminal.
2. Here is the code:
3. And here is the outcome:
How to reproduce?
Terminal connected to open, history on all symbols deleted from disk before start-up
Indicator log from the moment of start
As you can see in less than a second from the moment of start the symbol data became available to the indicator.
How to reproduce?
Terminal connected to open, history on all symbols deleted from disk before start-up
Indicator log from the moment of start
As you can see in less than a second from the moment of start the data on the symbol became available to the indicator.
Afternoon!
In other words, SECOND is not time during the electronic trading?
In other words, with a synchronized symbol and synchronized time series, we cannot get
Bars(immediately) - is this normal?
(For me) it's a mistake.
2. When there is data in TERMINAL (see fig. all bars after March 16), we are forced to go to server, is this normal?
The inconvenience and the long time it takes to get the information(for me) is obvious.
Good afternoon!
So a SECOND in e-commerce is not time?