Quote from: DJ Omnimaga on November 27, 2010, 01:54:48 pm

Quote from: ScoutDavid on November 27, 2010, 01:53:15 pm

Quote from: aeTIos on November 27, 2010, 01:52:42 pm

yes

That's a very uncomprehensible reply now, is that a 'yes it works very good scoutDavid, you rule'?

That would pretty much be the same thing, aside from the you rule part

It was, of course, a joke. I'm now printing this code and will then implement it in my code.

Now, I still have to divide a 16*16 sprite I have into 4 8*8 sprites to make a loading screen (not needed but it's professional)

USE lordconiupiters 16*16 sprite drawing routine, if you dont use grayscale.
Link: in a minute

The first thing you need to consider is that the drawing of Pic1 at (0,0) is still there, even after you draw it again.
So (unless you want the old one to remain) you have to do one of two things: (There might be more, these are the two that have occurred to me.)
1) Store a copy of the screen before Pic1 was drawn at all to, say, L3 (the backbuffer). Draw Pic1. When you want to move Pic1, copy the backbuffer to the main buffer. This will effectively remove Pic1 from the screen. You can now draw Pic1 in its new location.

This is the "method" I mentioned

I reread the thread and couldn't find your 'methods', so here is a new idea:

Code: [Select]

:[38107C1010282828->Pic1
:Pt-Change(0,0,Pic1
:DispGraph
:Repeat getKey(3)
:ClrDraw
:Pt-Change(0,10,Pic1
:DispGraph
:End
I added ClrDraw, that could work, right?

That should work, but I don't think it does what you originally intended. When you run it, what you will see is Pic1 appearing quickly once then disappearing at (0,0), and then it will display at (0,10), 10 pixels down, until you press right.

My confusion is that I thought you wanted it to start at (0,0) and only move to (10,0) after you press right. I thought that, after that, you wanted it to continue to move right every time you pressed right.

The max is 80, I think. If it's at 90, then part of the sprite is cut off.
However, the condition for the loop won't work. "Repeat getKey(3)" means that it does the loop until you press right. That means that, when you press right, the sprite doesn't move, but the program exits
Edit: 1400^th post!

Now it repeats until you press any key, and you're no longer using direct input, which means you can only read one keypress at a time.
For the condition of the Repeat, you should choose a key that quits the program and use that as the condition of the Repeat loop.

The first one is needlessly complicated and doesn't work anyway, so let's focus on the second
The main problem in the second one is that you're only checking for the key once. (The Repeat loop just waits for a key to be pressed, then continues, the key stored to Z)
Note: I'll continue as if you've fixed it to check for a key each time around the While loop.
You can still use getKey(15) and getKey(3); you don't have to use just regular getKey.
Also, you're missing an End. (You have a While and an If, but only one End).
You'll want a DispGraph in there too (in the If statement)
Also, you're still drawing the sprite at (0,10), not (10,0). Axe takes coordinates as X,Y in the Pt-( commands, not the Y,X that BASIC uses.
Note: I'll continue as if you've fixed these problems too.
The code's very close to perfect, but you still have a problem: each time you press right, it draws the sprite at (10,0). Never at (20,0) etc., but always at (10,0).
You'll need to use another variable to keep track of Pic1's current X position, and add 10 to it each time. As you've stated, if it goes too far right, its X position should be reset to 0.

Okay, so I'm somewhat forcing you along (Sorry ), but does this help?

In Axe, just about all mathematics and comparsions are, by default, unsigned. And in an unsigned system, you can never have a value less than zero. What you need is a signed comparison.

he means >> and <<. the signed comparisons.