Hah, wow if that isnt spaghetti code i dont know what it I was jumping around with the find button to see if any of the Lbls called eachother in a loop or something.  Sometimes i was jumping around for 8 or more Lbls before i got to an end

Well more embedded subroutines certainly makes it nastier, but it saves space

Whenever you call a subroutine, you "push" the place its supposed to return to into the stack so it knows where to go back to in the code when it reaches the Return, which then "pops" the stack.  Also, I wasn't sure at the time of writing if he did use any assembly code which is why I was explaining it at a lower level.

Glad you found the error

I would rather use a lot of subroutines if I am gonna re-use pieces of code several times and it can save space. Otherwise, there's a lot of repetitive code.

Without sub-routines and sub-programs, stuff like this would be impossible.

Whenever you call a subroutine, you "push" the place its supposed to return to into the stack so it knows where to go back to in the code when it reaches the Return, which then "pops" the stack.  Also, I wasn't sure at the time of writing if he did use any assembly code which is why I was explaining it at a lower level.

Glad you found the error

aaah ok, thanks for explaining. Makes more sense now ^^

When I'm finished with it I'll make sure to post my project. It's a really nice (albeit BIG) sprite editor that can store multiple sprites of either 8x8 or 16x16, and has support for hex entry and live hex display

I,m glad you fixed it. Can't wait to see it in action

Also glad to see more and more Axe coders. I guess it was a good thing I work on that video

Nice ^^

Feel free to start a new thread for your project btw, since it might easily get lost in this topic in a week or two (due to the high post rate)

I generally just use SourceCoder, but it can screw up small 2,3,4, etc for list tokens.

Oh yeah that one, I never tried it personally so I can,t tell. In my early calc programming days, we used TI-Graph Link

Personally I prefer programmign on the calc, though. I type faster on it when programming in BASIC or Axe

I like using TI ProgramEditor for a few reasons. Firstly, the program is always stored on your computer and you don't have to worry about it's safety. Secondly, running it through an emulator that you don't have any important data on and that can't become damaged is always nice. Thirdly, you can view indented code much more easily, which I always do to make the program more understandable. Fourthly, there's no taking a minute to scroll from one part to another in massive programs, which is helpful for projects such as the monstrous sprite editor I'm working on now, the compiled code of which just passed 7,000 bytes. Finally, it's easy to move around code. This often comes in handy when I realize I perform certain actions multiple times in the program and that I could save space by instead making that code into a subroutine and just calling it from those multiple places.

EDIT: In response to DJ's post below me, you know it only takes all of like 3 seconds to drag and drop the file to the emulator.

What is the best way to go about resizing an AppVar but not losing the data that was in it before? I'm pretty sure that the pointer to an AppVar doesn't necessarily stay the same between re-initializations, so I just copy all the data to L₁ and then copy it back to the new pointer, but that will end badly if the AppVar becomes larger than the free RAM at L₁.