05-03-2022, 05:00 AM
Hi Alexandre,
Thank you for finding a solution so quickly.
The main problem is that the browser's back button does not close a displayed form and removes it from memory, but only hides it from the user.
However, the application usually loses access to the form and the next time the application calls it, a new form is created if the new() call does not fail completely.
With extensive user navigation, the application also takes up an unnecessarily large amount of memory.
In addition, it is therefore certainly useful to check before creating a new form whether an initialized form already exists that can be used.
I have adjusted the test example accordingly.
Regards
Thank you for finding a solution so quickly.
The main problem is that the browser's back button does not close a displayed form and removes it from memory, but only hides it from the user.
However, the application usually loses access to the form and the next time the application calls it, a new form is created if the new() call does not fail completely.
With extensive user navigation, the application also takes up an unnecessarily large amount of memory.
In addition, it is therefore certainly useful to check before creating a new form whether an initialized form already exists that can be used.
I have adjusted the test example accordingly.
Regards