0 Members and 3 Guests are viewing this topic.
Quote from: calcdude84se on September 20, 2010, 09:13:18 pmQuote from: Quigibo on September 19, 2010, 05:54:16 pmWell apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it. I will have to find the name of that string. The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.There isn't a way to fix the memory leaks since this is an OS call.As you are probably aware, there is a leak-free (or less so) version of _GetKey, undocumented and called _GetKeyRetOff I wonder if something similar exists for the input bcall...Good luck making it work! If it's undocumented, does it means it won't work on the Nspire, though? I think Quigibo is aiming for full Nspire compatibility with the exception of the Full command.
Quote from: Quigibo on September 19, 2010, 05:54:16 pmWell apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it. I will have to find the name of that string. The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.There isn't a way to fix the memory leaks since this is an OS call.As you are probably aware, there is a leak-free (or less so) version of _GetKey, undocumented and called _GetKeyRetOff I wonder if something similar exists for the input bcall...Good luck making it work!
Well apparently the buffer where the input string is stored is not a temporary variable so a bcall to _CleanAll doesn't clear it. I will have to find the name of that string. The buffer for the input is named "-" and I've seen a "#" and "$" so I'm guessing it's something similar to that.There isn't a way to fix the memory leaks since this is an OS call.
Ah ok, I was a bit worried.Also,1000->XPause Xcrashes Kindermoumoute's calc. Could this be a bug on certain calc models or could it be his calc that is defect?
Oh ok, well in that case it's because 0= a pause of 65535, 1000=999, etc. Basically, to do a Pause that lasts nothing, you would need to do Pause 1. 65535 causes your calc to freeze for almost one minute, I think.
DJ, to be technically correct, 0 is a pause of 65536, 1000 is a pause of 1000, and so on
"This code acts like Axe 'Pause ', taking X for the amount. However, 15, not 65535, is the upper bound.Lbl SX-1+16not(X->XIf not(XGoto S
0->CLbl SX-1+16not(X->XC+1->CIf not(XGoto SDisp C