Are you going to make the label menu support up to 13 characters, as the new Axe version allows it ?

I don't know if it is a good idea or a bad one, since there won't be a lot of label columns on the screen if you support 13 chars, and I don't know if people will really use more than 5 chars
In fact, I think I'll only use 13 characters in my label if zStart supports it

Definitely no. This would totally break the way that I store them and I would only be able to support like 51 labels. (As opposed to 109).

Quote

OFFSCRPT.8xv (appVar) gets copied to $8001 every time the calculator turns off. This catches both 2ND + ON as well as APD. So instead of going to APD, it can just display your screen saver.

My OFFSCRPT always crashs the calc. The code is copied to $8001 and executed. But every times it reaches bcall(_jForceCMDNoChar) the calculator simply doesn't react anymore


I leaved the
bit   4, (iy + 8 )
out because this way the bit is set always and my code is never executed

The OS does not disable the LCD before calling OFFSCRPT.

Quote

OFFSCRPT.8xv (appVar) gets copied to $8001 every time the calculator turns off. This catches both 2ND + ON as well as APD. So instead of going to APD, it can just display your screen saver.

My OFFSCRPT always crashs the calc. The code is copied to $8001 and executed. But every times it reaches bcall(_jForceCMDNoChar) the calculator simply doesn't react anymore


I leaved the
bit   4, (iy + 8 )
out because this way the bit is set always and my code is never executed

Post the code, that's the only way I can tell what's wrong with it. Also, bit 4, (iy + 8) is the APD flag. I do RET Z because the code you're looking at was for a screensaver, and you wouldn't want a screen saver to run if you were turning the calculator off on purpose.

This one will freeze your calc after a BASIC input/prompt. So don't use it unless you want the Axiom.

What do you mean? (I can probably fix it)

Now hold on, I think one of the best parts of programming on the calculator is that it has tokens. People who program Axe or Basic frequently can tell you exactly how to get any command on the calculator in 3 buttons or less, and the fact that one token is comprised of perhaps 6 characters makes programming with tokens very quick.

In your program editor, you aren't using tokens though, and honestly, I think that is a mistake. The reason for this is that the TI-84 keyboard is a little awkward to type on. There are of course people who are quick with it, but those people are in the far minority (and they're faster with tokens). Also, without the token system, people actually have to memorize the names of functions, and while this won't be difficult for experience programmers, it puts a serious learning curve that wasn't there before on new programmers.

So, what I am saying is that if you want your IDE to become popular (and increase coding efficiency ) I think you should stick with tokens.

I made an axiom!!

This axiom is called zstaxe (clever, I know) and it allows Axe programmers to access the zStart assembly api. There are internally separate version for Axe programs and Axe apps, but externally you can't tell (other than a little discrepancy on the edit command).

Fpdf(progName) - runs progName using zStart, (this can also run apps lol)
    - progName - ptr to string - this is simply the name of the program with it's type byte
        - "prgmNAME" for programs
        - [14]"APPNAMES" for apps (apps are hard to get the name right, see note below)
  Outputs:
      - 01 - zStart not found
      - FF - program thinks it was run by a shell (and might require cleanup) (this can also mean progName not found)
      - 00 - program thinks it was run by the homescreen


Fpdf(progName, offset) - edits progName using zStart
    - progName - ptr to string
    - offset - offset in bytes into program to start editing (instant goto, resolves 2 byte tokens)
  Outputs:
      - program version - 01 - program or zStart not found - 00 - good to go
      - app version - this shouldn't return but if it does - 01 - no zStart - FF - no program
  Notes:
      - for the program version you need to quit back to the homescreen in order for it to actually edit the program (sorry, I can't fix this nicely)

Note about apps names:
   You need to match the app name perfectly, and what I mean by this is that all app names are actually 8 characters, and you need to figure out whether the extra ones are zeros or spaces. For instance: zStart is "zStart", 0, 0 and Calcsys is "Calcsys ". If you want to pad with zeros in axe, you need to do "zStart"[0000]. That will put the extra zeros on. So, the names of these two apps would be:
  - [14]"zStart"[0000]
  - [14]"Calcsys "


There's also a 2 byte memory leak in the current version of zStart, so I have a slightly updated version here for the axiom. The memory leak was making it crash.

This will work regardless of language:

Final = 0
Reps = int(log(Num))
for (A, 0, Reps)
    Next = int(Num / 10)
    Final = Final * 10 + Num - 10*Next
    Num = Next

I too am experiencing the whole "Buttons don't work" thing. OS 2.55MP, 84+. Happened only after i reinstalled zstart.

Oh, so I just tested it, and it apparently doesn't work when you combine zStart with MathPrint. The problem is definitely with zStart, but I have zero idea what would cause it. So try again with classic.

Is the program dependent on specific hardware revisions by the way?

Also does the speed difference occurs only with very large files? I tried ROL2 with the patch on and could barely notice much difference. However I was using an emulator. (Wabbitemu)

It's not dependent on the hardware at all.

It works on files of all sizes, but the bigger the file, the more noticeable the change is.