MT5 and speed in action - page 22
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
Let's go write everything from scratch in Asm yourself. It turns out to be OK, each of the libraries flies separately. But as soon as we start using them both at once, we start to get lags.
What is this?
Lack of understanding of reality? Infantilism or just trolling?
Yes, your libraries (yours exactly, as I understood perfectly) in monopoly mode spoil the life of the main programs. And instead of really describing "using my libraries kills the efficiency of the main code", the inefficiency game has started.
How long were you going to hide the real reason for the topic?
What's that?
A misunderstanding of reality? Infantilism or just trolling?
You're completely out of your mind to accuse a man who has constructively shown the weaknesses of the Terminal. How on earth was it possible to know about the internal architecture?
How long were you going to hide the real reason for the topic?
That's outright disrespect. Likewise.
You're completely nuts to accuse the man who structurally showed the weaknesses of the Terminal. How was it possible to know about the internal architecture?
Read the addendum above.
The real reasons must be clearly stated, otherwise the attitude will be appropriate. I did not speak out about cheating and the wolf ticket for nothing. When instead of the real reason people were slipped stories about XXX% brakes.
Like in your recent question about hiding names and direct deception of investors.
There are no stupid people on our side here.
The real reasons have to be made clear, otherwise the attitude will be appropriate. I did not speak out about cheating and the wolf ticket for nothing.
There was a clean MQL5 code reproducible by many people. Study the chronology of the thread first, instead of playing conspiracy theories that someone needs you so much that he is willing to spend his time on you to pour dirt on you.
There was a clean MQL5 code reproducible by many. Study the chronology of the thread first, instead of playing the conspiracy game that someone needs you so much that they are willing to spend time on you to pour mud on you.
You've spent so many years proving it - you're never a stranger to mucking up any issue.
Part of pure behaviour does not in any way mean that the rest of your posts are like that.
In case anyone doesn't get it, it's the fxsaber library which when applied in someone else's code gives brakes.
Instead of explicitly pointing this out, he started playing the game about platform braking and slipping suicidal examples. And when there was an opportunity to get to the real cause and mitigate the issue, he didn't take it.
For the sake of local optimisation, he poisoned the history cache for the main application.The main thing is that the cache has been speeded up.
It's just a shame that we're fighting again. It's more constructive without that.
The main thing is that the cache has been speeded up.
It's just a shame that we're fighting again. It's more constructive without that.
You don't have to substitute reasons, cheat and lie.
Then it would be constructive.
We're not defending our egocentric position here, we're developing a platform. Openly admitting mistakes and making amends.
You don't have to substitute reasons, cheat and lie.
Conspiracy, yes.
We're not defending our egocentric position here, we're developing a platform. Openly admitting mistakes and making amends.
Unfortunately, more often the former than the latter.
It's good that the cache has been sped up.