Erm...

UPDATE
Note that I didn't write "update" in red but in blue. This because this is not my work but Zero44's (I don't know why he didn't posted it himself by the way ).
Now you can send your Pokemons from a calc to another
See the "Link" folder in the zip.

(Nothing changed in my prog, no need to update it if you have the previous version, only care about the Link progs).

Also, if Zero44 could post here so he can get +1s...
(and if someone knows how to make a multicalc screenshot... o.o°)

edit: the download count is false: I already downloaded it three times to test

That looks great . Do they clip too ?

edit: ok it was a stupid question if people look at the screenshots but there is no screenshot in the first post as far as I can tell, and it still says "almost done" for clipping so I don't see any reason for being downrated.
"Fixed" by hellninjas

I just thought that the more there are games for Ndless, the more TI will see that we don't care about cheating and also, the more people will be interested in Ndless and pressure TI not to block it. However, I am not sure if that would make them change their mind.

So don't show them you were beaten by giving up your projects, but keep on programming (without making cheating programs )

edit: I corrected a mistake: there was a "us" instead of a "them".

I think I'll give up with this project, since TI blocked ndless
It would be useless to spend time for this if nobody will use it...
Sorry.

Why can't TI understand that it won't annoy them to allow 3rd party native code ?

I can't force you to continue but I think that continuing would be a good idea. It would show TI that developpment using Ndless 3.1 has always been about games, and not cheating.

Yes if you use zStart.
There is even an option "Compile, launch and come back to the editor".

c'est plutôt bien optimisé en général.

Moi, je code optimisé !?! Lolwat ?

Elles seront juste remplacées lors de la compilation. Comme je ne sais pas si tu compte les modifier (avec des map 512*128 ou 1024*64), j'ai pas fais la modification.

C'était exactement mon but, J'ai juste mis 256*256 pour le test


Sinon, j'ai juste trois problemes avec ton code.
-D'abord, tous les APPV sont bizarres, on dirait qu'il (ton code ou ton logiciel) a inventé un token "PV" et il ecrit APPV comme A,P,PV si tu vois ce que je veux dire.
-Ensuite, au moment ou tu fais 255→{APPV}→{APPV+2}→{APPV+257}→{APPV+97} etc, au moment ou Axe lit la deuxieme fleche HL a change et vaut APPV, il semblerait alors qu' au lieu de mettre 255 dans {APPV+2}, il mette APPV dans {APPV+2} puis APPV+2 dans {APPV+257}, etc, car il n'affiche pas ce qu'il faudrait sur l'ecran mais il l'affiche la ou il faut. Mais on s'en fiche car c'etait juste pour le test
-Enfin, j'arrive plus a bouger la carte vers la gauche
Apparement cela vient de la ligne "If XMAP and getKey(2)". En remettant "If XMAP=/=0 and getKey(2)" tout fonctionne.


Autre chose qui n'a rien a voir avec tes modifications, il y a un conflit de touches: bouger la map en meme temps vers le haut et la droite ouvre le menu curseur -.-°
Appuyer sur ces F2, haut et bas en meme temps semble "appuyer" sur F3 aussi, d'apres le programme de zTrumpet.

It's definitely possible, but also likely to be less efficient, since Axe's routines are designed around the various quirks of the 84+. It would still run faster on the nspire, but probably not as fast as C, def. not as fast as assembly.

Ok for "hardware things" but for example, I guess (I said "I guess") that Axe's mathematic operations won't need to be changed to run on the Nspire.

Least efficient, but most compatible way would be to have an 83+ emulator

Lol, yeah, but the color ?

This OS looks great, but I have to stay with ndless. It's extremely tempting though.

I think they made it on purpose so you think about giving up Ndless. But I don't upgrade unless they include a GBC emulator in their OS.