#EMU48 SHORTCUTS CODE#

I'd done exactly this in most of the rest of my code, but in this one function I'd forgotten that. Just wait for a key and loop if one doesn't turn up, go back to the beginning of the wait loop, which simply looks for a key. Don't draw bits of the screen, then wait for a key, then redraw the screen, wait, etc. In short, the loop you use should be really short, and shouldn't involve anything else except waiting for a key. This can have an impact if the program asks you to choose from a list of choices, and you've put the calculator into a busy loop so you can make it actually wait for a key to be pressed. It only seems to wait for about a tenth of a second, though I'm not sure if the speed of the calculator matters. If it doesn't see that one's been pressed, then it'll simply return 0 and exit, and won't wait around until a key has actually been pressed. Casio BASIC has a function called GetKey that looks to see if a key's been pressed while it's running (that's important), and pass back the value.

#EMU48 SHORTCUTS CODE#

One bug I had in my code relates to just how fast the calculator works, meaning that if I keep it too busy doing other stuff, it's got less time to take notice of something happening when I need it to. I've made several changes in it over the years, yet I'm still striking some of the same issues today that I did when I first started development. This is certainly true in a program I've been developing since before 2008. Thankfully I think I'm finally getting my head around Casio BASIC.Д¬omputer programs (and calculators too) spend 95% of their time waiting for user input. It can be a complete and utter pain if you get something wrong, and can be even worse if you don't know the language you're supposed to be working in. Writing programs can be pretty rewarding, when everything works right the first time. Programming the Casio fx-9750gII Everything should be made as simple as possible, but no simpler (Einstein)

Emu48 shortcuts