Posté le 25/04/2025 19:42
Planète Casio v4.3 © créé par Neuronix et Muelsaco 2004 - 2025 | Il y a 92 connectés | Nous contacter | Qui sommes-nous ? | Licences et remerciements
Planète Casio est un site communautaire non affilié à Casio. Toute reproduction de Planète Casio, même partielle, est interdite.
Les programmes et autres publications présentes sur Planète Casio restent la propriété de leurs auteurs et peuvent être soumis à des licences ou copyrights.
CASIO est une marque déposée par CASIO Computer Co., Ltd
Citer : Posté le 25/04/2025 22:12 | #
Can you please specify which model you're running on and potentially provide a full program to test with?
Please note that the base case would be gint_setrestart(1) and then just return 0. Calling gint_osmenu() goes into the menu without exiting the main() function. Normally, calling gint_osmenu() is the superior solution compared to using gint_setrestart(). It seems a bit weird that you'd need to use both.
Citer : Posté le 27/04/2025 12:17 | #
okay so i just use return 0 and it works, but i when i go into the app again, it shows the last thing it showed before it shut off until i press a key and then it works as if i just started it again. Is that normal?
Citer : Posté le 27/04/2025 12:53 | #
Yes it is normal. The state is save and restored. You need to update after returning to the addin
Citer : Posté le 27/04/2025 13:24 | #
can i update it automatically somehow
Citer : Posté le 27/04/2025 18:30 | #
okay so i just use return 0 and it works, but i when i go into the app again, it shows the last thing it showed before it shut off until i press a key and then it works as if i just started it again. Is that normal?
Not really, with gint_setrestart() when you come back it runs main() again. If main() draws a frame before it waits for input you shouldn't have this key-waiting period.
Note: you might be running into a limitation of gint_osmenu() however.