mappi1589 #: a forex factory calendar xml, it works almost everytime but randomly it show that error. Can I do something to avoid the error or run the code again if it detect that error again?
You could tweak the library to catch this problem and return NULL in createSibling(), but you would have to fix the calling point to deal with it. And possibly you could have other issues.
This error probably appears because you get a wrong XML answer from time to time, so in my opinion the best solution is to check for that beforehand.
You could tweak the library to catch this problem and return NULL in createSibling(), but you would have to fix the calling point to deal with it. And possibly you could have other issues.
This error probably appears because you get a wrong XML answer from time to time, so in my opinion the best solution is to check for that beforehand.
Thank you for your answer Alain, ok I will check if I can solve the error by checking the xml answer.
File EasyXmlIntegrator.mq5 Compiles with error on line 28.
28: sOutput += (ActualNode.getValue()) ? " Value: '" + ActualNode.getValue() + "'" : ""; Error:
cannot implicitly convert type 'string' to 'bool' examples_integration.mq5 28 27 Why does the code not compile without error?
How to fix?
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
a forex factory calendar xml, it works almost everytime but randomly it show that error. Can I do something to avoid the error or run the code again if it detect that error again?
You could tweak the library to catch this problem and return NULL in createSibling(), but you would have to fix the calling point to deal with it. And possibly you could have other issues.
This error probably appears because you get a wrong XML answer from time to time, so in my opinion the best solution is to check for that beforehand.
You could tweak the library to catch this problem and return NULL in createSibling(), but you would have to fix the calling point to deal with it. And possibly you could have other issues.
This error probably appears because you get a wrong XML answer from time to time, so in my opinion the best solution is to check for that beforehand.
Thank you for your answer Alain, ok I will check if I can solve the error by checking the xml answer.