Take a broader view. In addition to the calculation of indicator data, there are also set alerts, other user actions that should not change with timeframe changes. How to deal with them?
Write in global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, i.e. unambiguously wait for a new one.
ps. double-variable is 64 bits = 64 button-switches can be stored in one global variable.
Write to the global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, i.e. unambiguously wait for a new one.
ps. double-variable is 64 bits = 64 button-switches can be stored in one global variable.
That's how we're discussing the topic because without crutches there's no fucking solution. I already have all sorts of crap to get around the paucity of a programming language. And I wanted an evolution.
This is why we're discussing the topic, because without crutches, we can't solve shit. I already have a lot of crap to get around the paucity of the programming language. And I wanted evolution.
In the very beginning it was about writing structures - eitherFileWriteStruct or through a union like any file.
Then I should add: restarted from scratch and manually re-keyed all values to restore the whole context 😊
well... if it's such a complex calculator, then yes, you have to save the file, but somehow I'm sure a few clicks will be enough. (or a few global variables to save what the user clicked)
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.
Take a broader view. In addition to the calculation of indicator data, there are also set alerts, other user actions that should not change with timeframe changes. How to deal with them?
Write in global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, i.e. unambiguously wait for a new one.
ps. double-variable is 64 bits = 64 button-switches can be stored in one global variable.
Write to the global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, so definitely wait for new one.
Better yet, write to globals and back them up to objects because sometimes globals crash on unexpected events (terminal crash, power outage)
Write to the global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, i.e. unambiguously wait for a new one.
you're on a quest to "backup/restore or transfer to another terminal without once mashing":-)
You will be on a quest to "backup/restore or transfer to another terminal without ever swearing":-)
Not at all, practically no one needs it.
Better yet, write to globals and back them up to objects because sometimes globals get knocked out by unexpected events (terminal crash, power outage)
restart from scratch, no big deal
Write to the global variables of the terminal, read objects from the chart.
Startup alerts can't (shouldn't) happen, i.e. unambiguously wait for a new one.
ps. double-variable is 64 bits = 64 button-switches can be stored in one global variable.
That's how we're discussing the topic because without crutches there's no fucking solution. I already have all sorts of crap to get around the paucity of a programming language. And I wanted an evolution.
This is why we're discussing the topic, because without crutches, we can't solve shit. I already have a lot of crap to get around the paucity of the programming language. And I wanted evolution.
In the very beginning it was about writing structures - eitherFileWriteStruct or through a union like any file.
restart from scratch, no big deal
Then we should add: restart from scratch and manually reset all values to restore the whole context 😊
Then I should add: restarted from scratch and manually re-keyed all values to restore the whole context 😊
well... if it's such a complex calculator, then yes, you have to save the file, but somehow I'm sure a few clicks will be enough.
(or a few global variables to save what the user clicked)