This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Runer112
Pages: 1 ... 140 141 [142] 143 144 ... 153
2116
« on: July 25, 2010, 11:04:10 pm »
Drawing sprites to an arbitrary buffer would be nice. I'm working on a game that will require at least 2 extra buffers, and I'm sure that writing my own sprite routine in Axe would be nowhere near as compact/fast as your built-in sprite drawing routine.
2117
« on: July 24, 2010, 12:20:18 pm »
"Disp G" would attempt to display a string starting at memory address G, which would be between 0 and 56, so it would display whatever data is stored there (I'm not sure what's stored there, maybe someone else could tell you) until it hits a zero byte (end of string marker).
What you want is "Disp G▸Dec". This displays the value of G as a 2-byte integer.
2118
« on: July 23, 2010, 02:01:25 am »
It appears that if the last line of a source file is storing a value to a constant pointer, a bad symbol error is thrown if a closing brace is used. The error isn't thrown if the closing brace is omitted.
Some examples that would throw an error:
.AXEPRGM
0→{L₁}.AXEPRGM
[Pic0]→Pic0
A*2→{8*12+Pic0}
Some examples that would not throw an error:
.AXEPRGM
0→{L₁.AXEPRGM
[Pic0]→Pic0
A*2→{8*12+Pic0}
Pause 5000.AXEPRGM
0→{L₁}r.AXEPRGM
Copy(L₃,L₆,{2+L₂}
2119
« on: July 19, 2010, 03:08:42 pm »
So if we can't use DispGraphrr in interrupts, does anyone have any tips about ways to ensure that grayscale screen updating runs constantly and smoothly? Perhaps some trick to activate the screen update using an interrupt but not actually performing the update inside the interrupt?
2120
« on: July 18, 2010, 11:45:55 pm »
I don't quite remember, can you not use DispGraph/DispGraphrr in interrupts? I was just wondering because I thought I remembered seeing something like this, although it seems like it would be a good way to ensure smooth grayscale.
2121
« on: July 15, 2010, 03:32:17 pm »
*Drops a pin*
Oops, my bad
2122
« on: July 05, 2010, 06:18:37 pm »
This isn't a problem with the parser, just the Auto Opts file. Try to spot the (once seen, very gross) error:
SHORT means less than 256 bytes
CONST means any size
=/= is a "not equal sign"
>= is a "greater than or equal sign"
<= is a "less than or equal sign"
2123
« on: July 05, 2010, 02:39:45 pm »
I'm not entirely sure if this is a bug report or a feature request, but attempting to use a negative number in a Data() array returns a bad number error. (This occurs even if you use an r modifier)
2124
« on: July 04, 2010, 07:04:21 pm »
Protip
At the start of the program:
"prgmPROGSRC"→Str0
Archive Str0
At the end of the program:
UnArchive Str0
2125
« on: July 03, 2010, 02:13:21 am »
I meant to point out the wording, divide (/) it by half (1/2). 
2126
« on: July 03, 2010, 12:52:29 am »
That would be nice indeed. On the computer you can get an estimate by taking the app computer file size and divide it by half, but it is not always very accurate
>divide it by half
2127
« on: July 03, 2010, 12:50:34 am »
Actually I was looping through bytes and inverting them, although I was using {pointer} xor 255→{pointer}. I forgot 255 xor X=255-X, but I'll use the subtraction because it's smaller and probably faster.
2128
« on: July 02, 2010, 01:08:50 am »
I'm starting an on-calc Axe program editor, and the first part is displaying the program correctly, so I have to deal with tokens. With any luck I can get it to work and start adding features like sprite previews, subroutine/data collapsing, copy/paste, and maybe even real-time syntax checking.
2129
« on: July 02, 2010, 12:35:40 am »
No, that would return the pointer to the start of the created data. Also, as far as I know Axe does not support creating programs with GetCalc() yet, only appvars.
2130
« on: July 02, 2010, 12:25:07 am »
And to read programs, you first read the size field of the program and then you'll know when you've reached the end.
You mean the two bytes before the program start? EDIT: Text() works fine, it handles both one-byte and two-byte tokens correctly, determining which kind is pointed to and correctly displaying it. EDIT 2: Another question: Where are character/token small font sizes stored? Those would be nice to be able to access, even if manually for now, because I'm trying to print to the screen token by token and I'm wondering how the operating system handles advancing the pen correctly.
Pages: 1 ... 140 141 [142] 143 144 ... 153
|
Show Posts