I did have to change a speed variable though. Cubefield detects PCspire as a CX, so it set a variable to make the whole program go faster. This will probably also be a problem in TINCS, and isn't really fixable (well, cubefield's code needs to be changed).
Ruler: the timer that most programs use to time stuff is the same. And keyboard input is set to the same rate. So in theory, all programs should act quite the same.
Just wanted to show a little project I'm busy on. As some of you know, I mainly develop on Linux. This means testing Nspire Lua programs is a bit harder. Nspire_emu works fine, but there is no mouse support. That is why I set out to create something to run Lua programs natively (meaning without emulation) on my computer. I started 3 days ago, and here is the result:
Spoiler For screenshots:
(Colors are bad because of screen recorder)
EEPro (under dev) runs pretty good
Tetris:
Even different screen sizes if the lua script supports it:
And today I added a debugger:
( gvars() is a custom function of me that prints classes and/or objects )
I use the Löve Lua framework, since it was also event based and that made stuff a bit easier.
I personally (although I never tried a Prizm) prefer a CX. One of the main reason it because hardware wise it beats the nspire -- but of course you will only be able to take advantage of it with ndless. But I don't mind to wait for new version of Ndless, and I know that ExtendeD is dedicated to it. There has been an Ndless version for every OS IIRC. And Lua is growing bigger and better, both by input of the community and TI.
As others have said, the CX (with/without CAS) just beats the Prizm in calculator terms.
Loadstring is not the correct thing to use here, there is something much better. You need to know that every function, table, variable, etc is part of a table. string.char is the same as string["char"]. _G is reference to the global table, the table that contains string, math, spell_bolt and other variables. You can do something like this instead of using loadstring:
I think most games don't need multiple tabs. However, I think non games can use it perfectly. As Spyro stated, I have the interpreter and editor of LogoMagick on different tabs. I think it's fine like that