Axe imports all rows of tha picture. That feature was added on my request So you can do

Code: (Axe) [Select]

GetCalc("Pic1",768)
Copy(L6,P,768)

and even when you recall a pic with RecallPic # in TIOS, 64 rows will be drawn to the screen when the size of the Pic is 768!

RecallPic does not draw the 64th row, even if it exists.

I think he's asking what the gate is?  Note that not all 16 combinations have names

http://en.wikipedia.org/wiki/Truth_table#Truth_table_for_all_binary_logical_operators

Just some minor stuff. None of these improve size, but they'll shave off a few cycles.

p_Add510:
.db 4
inc h
inc h
dec hl
dec hl
p_Add514:
.db 4
inc h
inc h
inc hl
inc hl
p_Add767:
.db 4
inc h
inc h
inc h
dec hl
p_Add769:
.db 4
inc h
inc h
inc h
inc hl
p_Add1024:
.db 4
inc h
inc h
inc h
inc h
p_Sub510:
.db 4
dec h
dec h
inc hl
inc hl
p_Sub514:
.db 4
dec h
dec h
dec hl
dec hl
p_Sub767:
.db 4
dec h
dec h
dec h
inc hl
p_Sub769:
.db 4
dec h
dec h
dec h
dec hl
p_Sub1024:
.db 4
dec h
dec h
dec h
dec h

BUG:  Don't Quote Me!

I show best by example.


Text(5,10,"HELLO"
Text(5,30,"WORLD!"


When compiled it will give an ERROR: BAD SYMBOL  at the 2nd Text(

The parentheses are not closed.

The error occurs when the quotes are closed but the parentheses are not closed. It's completely understandable that you would have an error in this situation because you didn't close the parentheses. The fact that the code compiles correctly with both the quotes and the parentheses left open is just some odd quirk that probably should not be relied on.

I think X and Y are reversed when you try to use Pt-On with an arbitrary buffer.

Code: [Select]

[FFFFFFFFFFFFFFFF]->Pic1
.Pic2 is the buffer
Zeros(768)->Pic2

.Draw the sprite to Pic2
Pt-On(50,10,Pic1)->Pic2

.Copy Pic2 to the buffer
ClrDraw
Copy(Pic2, L6,768)
DispGraph

What I think should happen is it draws the sprite 50 pixels right and 10 pixels down. What actually happens is it draws the sprite 10 pixels right and 50 pixels down. Is this a bug, or am not doing this the right way?

I'm using Axe 0.4.6.

Yeah, this quirk has existed since drawing sprites to arbitrary buffers first came out. I believe it's been mentioned in here a few times before, but maybe there's a reason Quigibo is leaving it like this.

BUG:  Don't Quote Me!

I show best by example.


Text(5,10,"HELLO"
Text(5,30,"WORLD!"


When compiled it will give an ERROR: BAD SYMBOL  at the 2nd Text(

I fiddled around with it for a while, and to make it work, you have to change it to this V

Text(5,10,"HELLO
Text(5,30,"WORLD!

What is that about?

also i tried this, and it compiled.
Text(5,5,"ERROR: YOU HAVE TOO MANY NOTES"POO
( i know but i use the word poo when testing things....

the only thing that showed up was that square symbol..

A much more reliable way to avoid errors regarding closing quotes/parentheses/brackets is to simply close them all. You will never get an error this way.

---

Regarding this:
Text(5,5,"ERROR: YOU HAVE TOO MANY NOTES"POO

Once you closed the string, the parser resumes normal evaluation. This causes it to evaluate P, O, and O as variables, each one replacing the previous value. This results in the final value taking on the value of O, thus the code displays whatever garbage string is pointed to by O.

In case that's somewhat difficult to understand written out, here's pseudocode to represent how the parser interprets that line, instruction by instruction:
Load 5
Store last value into pen X
Load 5
(An instruction that's not important for this simplified pseudocode)
Store last value into pen Y
Load pointer to "ERROR: YOU HAVE TOO MANY NOTES"
Load value of P
Load value of O
Load value of O
Store last value into string pointer
Display string