Post Reply 
HP50g "Busy Bug"
02-12-2016, 04:05 PM (This post was last modified: 02-12-2016 04:08 PM by Han.)
Post: #11
RE: HP50g "Busy Bug"
If you type fast, using the (rightarrow)KEYTIME command might be useful. I would place the program << 0. ->KEYTIME >> into a variable named 'STARTUP' to ensure that there are no missed or double keypresses.

Graph 3D | QPI | SolveSys
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
HP50g "Busy Bug" - Vtile - 02-12-2016, 12:50 PM
RE: HP50g "Busy Bug" - toml_12953 - 02-12-2016, 01:21 PM
RE: HP50g "Busy Bug" - Vtile - 02-12-2016, 01:29 PM
RE: HP50g "Busy Bug" - damaltor - 02-12-2016, 02:02 PM
RE: HP50g "Busy Bug" - Vtile - 02-12-2016, 02:17 PM
RE: HP50g "Busy Bug" - Simone Cerica - 02-12-2016, 02:45 PM
RE: HP50g "Busy Bug" - Vtile - 02-12-2016, 02:52 PM
RE: HP50g "Busy Bug" - Simone Cerica - 02-12-2016, 02:58 PM
RE: HP50g "Busy Bug" - Vtile - 02-12-2016, 03:09 PM
RE: HP50g "Busy Bug" - DavidM - 02-12-2016, 04:23 PM
RE: HP50g "Busy Bug" - Simone Cerica - 02-12-2016, 03:14 PM
RE: HP50g "Busy Bug" - Han - 02-12-2016 04:05 PM



User(s) browsing this thread: 1 Guest(s)