Touching? Or overlapping? Here's overlapping:
If (X-Z+3≤6) and (Y-θ+3≤6)
  .Sprites are overlapping
End

And here's touching:
If (X-Z+4≤8) and (Y-θ+4≤8)
  .Sprites are touching
End


Yes, an infinite loop. The check in a For() loop consists of checking if the variable's value is greater than the upper bound. However, because a 16-bit number can never be greater than 65535, the condition will never be met and the loop will never end.

EDIT: If you need a loop with those bounds, use this instead. It's smaller, faster, and stronger too! (Well, maybe not stronger)

0
While 1
  →Q

  ;Put your code here

End!If Q+1


And here's touching:

Code: [Select]

If (X-Z+4≤8) and (Y-θ+4≤8)
  .Sprites are touching
End


I'm interested in this code, what would the variables mean? Only one of the object moves (coordinates X and Y) and the other object is stopped (C for it's x position, E for it's y position), but this is in my code.

I guess X=X, Y=Y and Z=E and θ=C?

Thanks

I didn't get it

I have a sprite at the coordinates (C,E). That sprite is still.
I have a sprite that moves and I need to check if the moving sprite touches the other sprite, the moving sprite's coordinates are (X,Y).

I tried this:

If (X-C+4<=8) and (Y-E+4<=8)
  Return
End

It didn't work though

The context is:

24→C
24→E
Repeat getKey(15)
If (X-C+4<=8) and (Y-E+4<=8)
  Return
End

.MORE COLLISIONS

.GETKEYS FOR THE MAIN SPRITE

.DRAW FLAG
Pt-On(C,E,Pic1)

.THE MAIN SPRITE
Rect(X/256,Y/256,4,4)

.DISPLAY IT ALL
DispGraph
End

So the main sprite moves with the keys, I want it when I touch the Pic1 (at coordinates (C,E)) the program closes.

Woo! Thanks a lot calc84maniac and Runer112 I had to divide by 256 since it was in x256 mode.

It is not safe to allocate/deallocate memory for an OS variable by just changing the size bytes. You'll probably want to use MemKit's Delete() function, which is able to deallocate a specified number of byte from an OS variable.

When the variable was created, the OS allocated just the right amount of size to contain it. It uses that size to know how far after it in memory to store the next variable, and how much of memory to free up when the variable is deleted or archived. If you alter the number, it will result in either a memory leak or the variable overlapping another variable. The next time the OS tries to overwrite the variable, delete the variable, or rearrange the contents of RAM, there will likely either be a memory leak left in RAM or part of another variable will be overwritten.