Author Topic: Features Wishlist (Read 682783 times)

Darl181 · « **Reply #1920 on:** March 01, 2011, 08:18:09 pm »

Something that would be nice: run indicator going while it's in the process of "Writing APP..."
Occasionally it seems frozen

Also, lowercase letters usable in static pointers GDB, Str, and Pic would really help

calc84maniac · « **Reply #1921 on:** March 01, 2011, 08:21:46 pm »

Quote from: Deep Thought on March 01, 2011, 06:40:38 pm

Quote from: Compynerd255 on March 01, 2011, 11:13:23 am
Quote from: Deep Thought on February 28, 2011, 08:53:27 pm
Request: Adding a null byte after input.
You could always add that yourself. In fact, you are probably doing character processing on the string anyway, since input returns a string of tokens.

By then there's no way to know how long the string is, though.

Doesn't the returned string have size bytes just like any other variable? It's just a temporary string variable.

Deep Toaster · « **Reply #1922 on:** March 01, 2011, 08:54:41 pm »

I ... didn't know that

I thought it was stored in some safe RAM area. Guess I should have checked

squidgetx · « **Reply #1923 on:** March 02, 2011, 08:33:49 pm »

Something else; Normally Axe will save changes, but if you get a compile error and scroll to with prgm, it won't save any setting changes. This is sometimes annoying, at least for me, because often I find myself accidentally compiling apps...

Quote from: Darl181 on March 01, 2011, 08:18:09 pm

Something that would be nice: run indicator going while it's in the process of "Writing APP..."
Occasionally it seems frozen

^^ This. Especially since I have encountered scenarios where it really was frozen (well, I waited 10 minutes before pulling a battery, thankfully archive remained uncorrupted)

Quote from: calc84maniac on March 01, 2011, 08:21:46 pm

Doesn't the returned string have size bytes just like any other variable? It's just a temporary string variable.

Huh, I always thought it just pointed the appropriate location in L5.

Compynerd255 · « **Reply #1924 on:** March 03, 2011, 10:19:52 am »

I have another cool feature request - you don't have to do this if you don't want to.

I'd like an auto-updating version number in the standard Major.Minor.Revision format. You would specify a version number to start counting from in the program, then the Revision would automatically update every time the program is compiled. Then, you could use this value in your programs (e.g. to make sure that two calculators playing a link game are playing the same version of the game).

aeTIos · « **Reply #1925 on:** March 03, 2011, 10:29:03 am »

Request: fixed input command (it sometimes adds extra bytes)

calc84maniac · « **Reply #1926 on:** March 03, 2011, 10:33:36 am »

Quote from: aeTIos on March 03, 2011, 10:29:03 am

Request: fixed input command (it sometimes adds extra bytes)

What do you mean, "adds extra bytes"?

Deep Toaster · « **Reply #1927 on:** March 03, 2011, 08:25:42 pm »

Quote from: aeTIos on March 03, 2011, 10:29:03 am

Request: fixed input command (it sometimes adds extra bytes)

It doesn't add extra bytes. You probably noticed that displaying it has some stuff that comes after it. That's because a string created by input isn't a null-terminated string like you're used to, where the string ends with a byte of [00]. Instead it's continuous with the rest of the data as a length-prefixed string, like with BASIC strings. In other words, instead of ending the string with a 0, the string has its own length stored in the two bytes preceding it. Use

Code: (Axe) [Select]

:input→P
:{P-2}r

to get the length of the string.

DJ Omnimaga · « **Reply #1928 on:** March 04, 2011, 02:46:00 am »

Quote from: Compynerd255 on March 03, 2011, 10:19:52 am

I have another cool feature request - you don't have to do this if you don't want to.

I'd like an auto-updating version number in the standard Major.Minor.Revision format. You would specify a version number to start counting from in the program, then the Revision would automatically update every time the program is compiled. Then, you could use this value in your programs (e.g. to make sure that two calculators playing a link game are playing the same version of the game).

The problem, though, is that some people could just cheat by modifying the game with calcsys. The only way to prevent cheating would be to scan the entire program via the link port and compare with your copy, to spot any differences. But again, this isn't very likely to happen since the average calc gamer at school barely even know how to archive/unarchive/turn ON the calc, anyway.

Quigibo · « **Reply #1929 on:** March 04, 2011, 02:57:07 am »

Quote from: DJ_O on March 04, 2011, 02:46:00 am

Quote from: Compynerd255 on March 03, 2011, 10:19:52 am
I have another cool feature request - you don't have to do this if you don't want to.

I'd like an auto-updating version number in the standard Major.Minor.Revision format. You would specify a version number to start counting from in the program, then the Revision would automatically update every time the program is compiled. Then, you could use this value in your programs (e.g. to make sure that two calculators playing a link game are playing the same version of the game).
The problem, though, is that some people could just cheat by modifying the game with calcsys. The only way to prevent cheating would be to scan the entire program via the link port and compare with your copy, to spot any differences. But again, this isn't very likely to happen since the average calc gamer at school barely even know how to archive/unarchive/turn ON the calc, anyway.

The goal isn't to prevent cheating though, its just to try to make sure the programs are compatible so that linking works 100%. Like if you changed your linking routine or something between versions.

This isn't really an Axe feature though, its really something the programmer should take care of themselves and its relatively trivial.

DJ Omnimaga · « **Reply #1930 on:** March 04, 2011, 03:00:50 am »

Oh, right, then I guess it could be nice, but I agree it might be best if the programmer handled this.

Runer112 · « **Reply #1931 on:** March 08, 2011, 05:46:47 pm »

thepenguin77's perfect grayscale tutorial brings up a good request: changing the display routines to advance in rows instead of in columns. Although this would possibly slow the routines down a bit, even without perfect crystal timer synchronization, this should make the grayscale look better.

yrinfish · « **Reply #1932 on:** March 12, 2011, 03:38:26 pm »

Another request:
An GetCalc() that returns a pointer to the VAT entry of it.
Something like:

Code: [Select]

:"prgrmBLAH"->Str0
:.NORMAL
:GetCalc(Str0)->A
:.POINTER TO VAT
:GetCalc(Str0)r->A

That r is the angle menu r

Ashbad · « **Reply #1933 on:** March 12, 2011, 03:40:23 pm »

that would be useful, to find out other attributes of the program stored in the VAT. however, if I'm not mistaken, there might be a simple way to do this in a few commands already (not sure, thought I saw something like that before.)

yrinfish · « **Reply #1934 on:** March 12, 2011, 03:54:21 pm »

That would be nice!!!
I want to use it to store sub-programs as an appvar and change them to a program when it is started.

Author Topic: Features Wishlist (Read 682783 times)

Darl181

Re: Features Wishlist

calc84maniac

Re: Features Wishlist

Deep Toaster

Re: Features Wishlist

squidgetx

Re: Features Wishlist

Compynerd255

Re: Features Wishlist

aeTIos

Re: Features Wishlist

calc84maniac

Re: Features Wishlist

Deep Toaster

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Quigibo

Re: Features Wishlist

DJ Omnimaga

Re: Features Wishlist

Runer112

Re: Features Wishlist

yrinfish

Re: Features Wishlist

Ashbad

Re: Features Wishlist

yrinfish

Re: Features Wishlist