Posté le 03/10/2025 18:28
Planète Casio v4.3 © créé par Neuronix et Muelsaco 2004 - 2026 | Il y a 154 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 03/10/2025 18:40 | #
Are you using GetKey() with the old official fx-9860G SDK or are you using getkey() from gint with the fxSDK? Please provide a MWE if you can.
In any case, it's quite unlikely for either of these functions to freeze because of the CPU type.
Citer : Posté le 05/10/2025 06:03 | #
GetKey() waits for an input in the SDK
need to use a custom keydown() function instead
Citer : Posté le 11/10/2025 20:33 | #
i use fxsdk and it happens when i use it in a function thats called from a while loop
Citer : Posté le 11/10/2025 21:37 | #
If you want instant feedback that doesn't pause until something happens, use clearevents() then keydown().
Citer : Posté le 18/01/2026 12:57 | #
Yes, it likely does. The fx-9860GIII uses the SH4A CPU, which isn't fully compatible with older fxSDK versions designed for the SH3 models. The GetKey() implementation might hang because of differences in hardware registers or memory mapping. Try checking if there’s an updated fxSDK version or specific fx-9860GIII support. Alternatively, look for community libraries or forum threads for custom input routines for the GIII.
Citer : Posté le 18/01/2026 13:27 | #
Complete nonsense. Keep your AI-style non-facts out of here.