If you include a program in axe source, like ↓
:.PROGRAM
:[stuff]
:prgmPROGRAM2
:[more stuff]Does Axe put a return after the sub-program, or do you have to put in the ret manually?

I love multiple programs in Axe, I just tried them.

I have an Axe question:

.POP
prgmPOPSTUP
prgmGKSRC
If pxl-Test(X,Y+5)
Return
End
Pt-On(20,55,[FFFFFFFFFFFFFFFF
Pt-On(X,Y,[FF42241800000000
End

1. I know I can use a Rect( instead of the Pxl-On(20,55. Is it faster/smaller?
2. The sprite at X,Y is 4 pixels tall, so why won't pxl-Test(Y+5) execute? The program is never closed, that if is never checked.
3. The prgmGKSRC is getKey movement for sprite X,Y (like If getKey(1):Y+2->Y) and I move the sprite all over the screen right ABOVE THE OTHER SPRITE, and still the program never closes.

What am I doing wrong?

1) Yes

2) If its 4 pixels tall, that means starting at the top left corner, there is a black pixel at Y+0,Y+1,Y+2, and Y+3, and there is white everywhere else.  Y+5 will *not* trigger.

3) Return does not close the program if you are inside a subroutine, are you inside a subroutine?

1) Thanks
2) I tried 4, didn't work
3) I am not in a subroutine and I changed 'Return' to other stuff, nothing worked.

Perhaps I should post all the code:

POPSRC
.POP
prgmPOPSTUP
Repeat getKey(15)
prgmGKSRC
If pxl-Test(X,Y+4)
Return
End
Pt-On(20,55,[FFFFFFFFFFFFFFFF
Pt-On(X,Y,[FF42241800000000
End

prgmPOPSTUP
..SETUP
Asm(EF4645EF7045FDCB00AE

prgmGKSRC
..GETKEYS
DispGraphClrDraw
If getKey(1) and (Y<60
Y+2->Y
End
If getKey(2) and (X>0
X-2->X
End
If getKey(3) and (X<88
X+2->X
If getKey(4) and (Y>0
Y-2->Y
End


Could it be that you are clearing the screen right before you pixel test, and that there hasn't been anything drawn to the screen yet?  Try doing the test after the sprite displays.  And also, stick with +4, I didn't realize you were trying to detect the *other* sprite

It worked perfectly! My program just became a lot bigger though :S

Old size: 497 bytes
New size: 528 bytes

The difference between old and new is a a or:

Old program:
If pxl-Test(X+3,Y+5
Return
End

New program:
If pxl-Test(X+4,Y+5 or ((pxl-Test(X+3,Y+5
Return
End

The 'or' is big in Assembly in seems.

Why did you add the second pixel test command?

My sprite is like:

MySprite:
 .db $FF
 .db %01000010
 .db %00100100
 .db %00011000
...


So it's like an arrow, but it's point  has two sprites. I'll change the sprite though =D

Also, I'm pretty sure that Rect( is much bigger than Pt-On(.

Size with Pt-On:
Pt-On(20,56,[FFFFFFFFFFFFFFFF
542 bytes
Size with Rect(:
Rect(20,56,8,8
650 bytes

Also, it's bigger, in this case, does it also mean it's faster?

Actually Rect() is smaller, but since you still have the other Pt-On in your program, it still has the Pt-On subroutine and is *also* adding in the Rect() subroutine, making it larger.  Also note that size doesn't necessarily have any correlation with speed, but smaller is in general faster.

It only uses the defines/subroutines it needs, smart Quigibo.

rand^n generates a number from 0 to n? Including 0 and n? Or from 0 to n+1? Wondering.

Also, can I have a Lbl B and a variable B in the same program and they won't be confused?