TI's AMS packs a famously powerful dialect of TI-BASIC. However, it still has its own problems, and one of those is the fact that a programmer cannot change the content of the status line on the bottom of the screen without resorting to use of an ASM program.
There are certain programs out there that can do this already, like Flib. However, many such programs do a lot more than just status line modification, and that does slow them down considerably due to additional initialization, which can be seen in Flib's code.
So, I fired up the TIGCC IDE and whipped up my own status line modification utility, statline, in about half an hour. It's really simple to use and takes up only 362 bytes on-calc.
From a few quick-n-dirty tests I determined that my program was certainly much faster than Flib. So I semi-formalized them, formatted all my 'research' (if you can even call it that) into a nice Markdown file, and put it all on GitHub. TL;DR: statline is ~183% faster than Flib in status line message modification tasks. I did not do benchmarks for other things like setting and clearing the BUSY indicator because I thought it would be a little pointless, but rest assured that statline also handles that (and the LOCK indicator, which Flib doesn't do) at some speed noticeably faster than Flib would.
There are certain programs out there that can do this already, like Flib. However, many such programs do a lot more than just status line modification, and that does slow them down considerably due to additional initialization, which can be seen in Flib's code.
So, I fired up the TIGCC IDE and whipped up my own status line modification utility, statline, in about half an hour. It's really simple to use and takes up only 362 bytes on-calc.
From a few quick-n-dirty tests I determined that my program was certainly much faster than Flib. So I semi-formalized them, formatted all my 'research' (if you can even call it that) into a nice Markdown file, and put it all on GitHub. TL;DR: statline is ~183% faster than Flib in status line message modification tasks. I did not do benchmarks for other things like setting and clearing the BUSY indicator because I thought it would be a little pointless, but rest assured that statline also handles that (and the LOCK indicator, which Flib doesn't do) at some speed noticeably faster than Flib would.