Cool to hear. As for saving in appvars they are the main reason why I quit Axe a few years ago and why Supersonic Ball lacks highscores. I just found the process too confusing because I always mixed up the syntax for saving with the one for reading appvars content and half of the time it wouldn't even work even with the right syntax. >.<

The issue is that it's easy to mix up both syntaxes so you end up swapping them by mistake and wondering for hours why your code doesn't work. In my case, I also always had the issue about reading from the wrong location and despite hours of help from Quigibo at the time, my tilemappers would never get close to working (in my case, either reading from appvar would read from the wrong location even if I pointed to the right location or my programs would just say Done when ran even with the right amount of End commands and the right shell selected, despite a full mem reset done beforehand).

A few years ago I always said this was a serious issue with the Axe language and that appvar saving/reading really needed a syntax overhaul because using the same token for two commands made things too confusing. One thing that should have been done is to not have both reading and saving use Getcalc() and have one of them use something else (maybe "SaveCalc()"?), to avoid confusion, or implement more error codes to make things easier to debug. Also another problem is that getting the commands order right in your code can be extremely tricky to remember, so the user will often put the getcalc command at the wrong location. Sadly, it is too late to change all of this because this Axe syntax has been around for 4 years and most hardcore Axe users have gotten used to it.

Yeah, didn't really run into such problems writing reuben either

So yeah, don't hesitate to ask

It is the same with other computer languages, you just open a filestream with either read or write (or both), the function call is the same. It might be originating from that.

I still think the Getcalc syntax should have been changed to something else closer to TI-BASIC or xLIB ...

How do you interface with appvars with TI-BASIC/xLIB? I glanced at the BASIC third-party library page on the DCS wiki and couldn't see any function names that jumped out as interfacing with appvars.

I'm adding a shop now . Also I really need help with Appvars....

Quote from: DJ Omnimaga on May 27, 2014, 08:11:15 am

I still think the Getcalc syntax should have been changed to something else closer to TI-BASIC or xLIB ...

How do you interface with appvars with TI-BASIC/xLIB? I glanced at the BASIC third-party library page on the DCS wiki and couldn't see any function names that jumped out as interfacing with appvars.

For example, if you want to create a game save, you just store the content you want in a list, such as L1->LSAVE. Of course you can't use appvars, but you can still create external files or read from them that way. As for reading from a save list, you do LSAVE(1) for element 1, LSAVE(2) for element 2, and so on (so you can do stuff like 18+LSAVE(2)->A).

With Celtic you can interface with appvars directly but the syntax doesn't look much better than in Axe. (IN axe, I think just making appvar save use a different token than appvar reading rather than have them use the same would already help).


But yeah, as Street said, if you need appvars help you might want to check the tutorial in the Axe sub-forum.