New MetaTrader 5 Platform Build 5200: Extended OpenBLAS support and enhanced control in MQL5 - page 6
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
EA crash after update mt5 to 5232, I compile the EA with this version and run it.
then I downgrade to 5226 and compile again, run at downgraded version, everything works fine.
Issues after the test ended with changing tabs on strategy test continue on 5232. See that I'm on M30, but have clicked on Daily tab.
Just a summary of scattered posts that I noticed, related to the "tabs" malfunction in the Strategy Tester ...
Has anyone noticed that the MQL5 Forge Git functionality, only considers Unicode/UTF16 files as valid (green check-mark after a commit)?
Other file formats, such as ASCII, UTF-8 (with or without a BOM) are successfully committed, but remain marked with a red warning bubble, even though on the forge they are all correctly updated and displayed.
Reference: Build 5200 ...
EA crash after update mt5 to 5232, I compile the EA with this version and run it.
then I downgrade to 5226 and compile again, run at downgraded version, everything works fine.
@Ilyas
checked build 5233, problem still there.
@Ilyas
checked build 5233, problem still there.
Thank you for your message.
Could you provide the source code or give me access to a repository with it?
Hi Ilyas,
Could you please review this or escalate it to be checked? This is something that happens to the vast majority of us, although many just solve it "silently". Still, as I mentioned, it really should be reviewed.
Thanks.
Forum on trading, automated trading systems and testing trading strategies
New MetaTrader 5 Platform Build 5200: Extended OpenBLAS support and enhanced control in MQL5
Fernando Carreiro, 2025.08.26 19:41
Has anyone noticed that the MQL5 Forge Git functionality, only considers Unicode/UTF16 files as valid (green check-mark after a commit)?
Other file formats, such as ASCII, UTF-8 (with or without a BOM) are successfully committed, but remain marked with a red warning bubble, even though on the forge they are all correctly updated and displayed.
Reference: Build 5200 ...
Sorry, I can't send the code, but I found where is the problem, let me explain:
I have a class CClassIndicators which is contain another complex classes and structures.
Somewhere in my code when I try this, Access violation error happens.
After some attempts, I figure it out how to solve the problem, when I changed to this, it works fine,
CClassIndicators temp; temp = m_main_obj; // works fineI follow your posts in Russian forum, about beta testing and bug report from Russian users also,
So my question is, shouldn't we get a warning or any error from the ME for this "CClassIndicators temp = m_main_obj" ? because after build 5200 I got some error for structure constructor(probably you already know about those errors).
So my question is, shouldn't we get a warning or any error from the ME for this "CClassIndicators temp = m_main_obj" ? because after build 5200 I got some error for structure constructor(probably you already know about those errors).
No, copy constructors are now generated implicitly if allowed.
Hi Ilyas,
Could you please review this or escalate it to be checked? This is something that happens to the vast majority of us, although many just solve it "silently". Still, as I mentioned, it really should be reviewed.
Thanks.
Probably, this behaviour has been fixed in the builds > 5200