Adrien Bertrand

Well, I "cheated", and was able to build a version with those two with only static libs and system libs. So, it should be good now, please try that @JWBstuhr...

I'll double check in TI-Connect CE as well but that seems correct indeed.

So according to https://github.com/TI-Planet/z80_basic_tokens/blob/master/tokens.csv > * if a string/appvar/(protected) program contains any CSE or CE tokens (like the colors), it should be `1A 0A 0F` > * Pictures and GDB's...

well it probably doesn't matter if it can't send them to older calcs since they wouldn't actually be compatible anyway (but if it does transfer some vartypes correctly despite that...

Well I guess we could probably keep 00 instead of 0A until we find a more accurate rule. But for the ranges I've noted above, there isn't any confusing cases.

Right, this then appears to be indeed a calculator product ID mapping directly, as @debrouxl mentioned. So, let's _only_ enforce the dedicated version byte on things we're sure are only...

Not yet unfortunately. Would you have a pseudo-code algorithm of what you think would be best to have in CEmu?

Alright, looks like it would be a feature of ti_vars_lib to be able to "compute" the minimum-compatible version, since that's an information specific to tokens. CEmu doesn't deal with that...

Just leaving that here for reference: The third byte is actually what's called the "owner calculator ID", and it can have the following values (that I have seen so far):...

Yes I know, it's in my edit of the comment above :P But I was just listing the values we've seen so far, although all of them may not really...