I believe that you store that data into another variable.
Then, use that variable normally.

[Pic1]->GDB1
EDIT: Also, does anyone know what DATA→NAME does? Use? Practical application?

Talking about translations, I can make a french version of the PDF. Is it OK with you, Quigibo?
I can also make it in russian, but I doubt that it will be useful...

I believe that you store that data into another variable.
Then, use that variable normally.

Code: [Select]

[Pic1]->GDB1
EDIT: Also, does anyone know what DATA→NAME does? Use? Practical application?

You just used exactly what you're asking about in that example.  [Pic1] is the "DATA" and GDB1 is the "NAME".

The problem with using an image in Axe is that unfortunately, the picture files only have 96x63 pixels, so it misses the last row.  Usually what you want to do is just add 12 bytes of white pixels to the bottom or top.  Here is how you display an image right now.  I think I will automate this in the future:

:[Pic1]->Pic1        ;Store the picture in memory call it Pic1
:det(12)             ;Add 12 zeros (96 pixels) to the bottom
:conj(Pic1,L6,768)   ;Copy all 768 bytes to the graph buffer
:DispGraph           ;Draw the buffer onto the screen

By the way, there is an even easier way to do it in 0.2.4 (not out yet) that I came up with.  You can draw any buffer to the screen directly without having to copy it to the main buffer first by doing this:

:[Pic1]->Pic1        ;Store the picture in memory call it Pic1
:det(12)             ;Add 12 zeros (96 pixels) to the bottom
:Pic1->DispGraph     ;Draw the picture directly onto the screen

EDIT: If anyone wants to do translations of any of the files that's fine.  But they aren't done yet, so they would have to be re-translated in the future so keep that in mind.

Thank you, Quigibo
Where could I find native assembly code written in hexadecimal?

So to make those codes on TIDB someone just wrote a program for them (in assembly) and then compiled them into hex?

Doesn't the .8xp file have to already be written in assembly?

Copying all those grayscale sprites took as long as writing the update almost

Even though grayscale was the main focus of the release, I've found that I've significantly decreased program size with the look-ahead parsing, it was surprisingly simple to write.  I also found a part that was supposed to be optimized but never was in the previous versions and just went unnoticed.  Well, I fixed that too.

Just an explanation for look ahead... there is a situation that you will never be in, but you might think its a bug if you try it.  Its intentional.  Whenever you add or subtract a constant to a pointer like: L1+5, it automatically groups this into a single pointer (L1+5) to minimize runtime calculations.  Constant + Constant = Constant so now it just replaces the number with what it should be before it compiles.  But, that changes the order of operations if you were to do some other operation on the left of the pointer.  Like 2*L1+5 is actually 2*(L1+5).  But you'll never end up doing that really becasue the only operation you ever do to pointers is addition and subtraction anyway.

As an example, Builderboy's Portal X code shrunk by about 6% (almost 500 bytes) with these optimizations alone.