Now by default all text is somewhat formatted before drawn on the screen, i.e. unnecessary spaces are removed. It can be removed for whatever reason using the NSP_FONT_NOFORMAT flag. Screenshot (the string used is the one in quotes of course):



I'll probably add word wrapping at some point too, not sure how cleanly it'll fit in the code. Speaking of cleanness, I've removed tab support, all font width/height getter functions I had at one point, and the textwrapping feature when using SDL_nDrawString(). That is because those features are very rarely useful, have inconsistent behavior and are a bitch to maintain and integrate. They would only be useful in console-type applications, and in that case nspireio should do the job. Removing them allows much cleaner and more robust code.

EDIT: After some further thought, I'll possibly add the string width/height getter functions again. It was especially the tab character that made me hesitate, but now that it's gone I guess I can clean those functions up. They might be useful for drawing centered text and whatnot.

Off-topic: Those tiles are nice. Are they from a game in particular or did you make them yourself?

Some free ones I found somewhere I can't remember.

Here's a screenshot of a little program I'm writing for a TI-Nspire SDL tutorial I'm working on:



I actually released 0.2.0 but didn't make it public, as I found some small issues (found them while working on the aforementioned program) that needed to be fixed, so the next public version will be 0.2.1, which should be out tomorrow if everything goes well.

Yup, as usual, this is good work

Relayed at TI-Planet, http://tiplanet.org/forum/viewtopic.php?t=8907&p=123755#p123755

is SDL easier to program than nspire c/asm?

Any progress in C++ support? 

Didn't certain C++ commands work on the Nspire though? I remember there was a post somewhere claiming some did...

Also nice update on this

Some updates...
I will probably release unexpectedly soon the following version, 0.3.0. I'm writing a lot of the video code for full compatibility on all calculators without the need to recompile (and not the slightest impact on performance). That means one program for all calculators. (it's quite a major change, hence the jump to 0.3.0 right away)
There's also a bug with uneven width images when using the array-based images that needs to be fixed.
I'll probably add a mode for easier porting that shows a message box when an error occurs, avoids mystical reboots and such.

Here's the Zelda example running on both machines in 8 bpp, same binary for both (and as you can see in the version, no more nSDL 0.2.0-8/16-cx wizardry):

That also means there'll be no NSP_BPP, so the user will have to specify the bit depth (if 16 bpp is used, it'll be forced to 8 bpp on classic models).

EDIT: here's the on-calc debug helper in action:

It shows all messages printed with NSP_DPRINT() and SDL_SetError().