(1) UninitializeReason() not always return to new launch init() what previous launch
deinit() sees, why?
previous launch deinit() sees: REASON_CHARTCLOSE
new launch init() sees: Script finished its execution independently
(2) EA global scope memory and EA any scope static memory
fails to reset to compile time initialization values every time init() called, why?
When UninitializeReason() returns REASON_CHARTCHANGE or REASON_PARAMETERS
EA global scope memory and EA any scope static memory are observed to retain values
from previous launch.
Both questions & observations are easily demonstrated, this is not my imagination.
I have programmed around above discovered issues - but... that is not answer for
all MT users, is it?
How many are getting unaccountable EA runtime descrepancies and needlessly spend
so much time in attempts to explain?
((Thank you irusoh1 (on 2006.10.30 19:28, 'int x = double y ?') for getting me back onto stable ground, post contents *always* in my mind whenever
get to point with MT where loose will to live :))
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.
(1) UninitializeReason() not always return to new launch init() what previous launch deinit() sees, why?
previous launch deinit() sees: REASON_CHARTCLOSE
new launch init() sees: Script finished its execution independently
(2) EA global scope memory and EA any scope static memory
fails to reset to compile time initialization values every time init() called, why?
When UninitializeReason() returns REASON_CHARTCHANGE or REASON_PARAMETERS
EA global scope memory and EA any scope static memory are observed to retain values
from previous launch.
Both questions & observations are easily demonstrated, this is not my imagination.
I have programmed around above discovered issues - but... that is not answer for all MT users, is it?
How many are getting unaccountable EA runtime descrepancies and needlessly spend so much time in attempts to explain?
((Thank you irusoh1 (on 2006.10.30 19:28, 'int x = double y ?') for getting me back onto stable ground, post contents *always* in my mind whenever get to point with MT where loose will to live :))