In a thingie I'm making, I need a mouse feature.

I'm using Qwerty55's code (thanks!):

:.This is the sprite
:[80C0A09088D0A818]→Pic1
:While 1
:.Store the screen to the back buffer
:StorePic
:.Display Sprite
:Pt-On(X,Y,Pic1
:DispGraph
:.Erase Sprite
:Pt-Change(X,Y,Pic1
:.Replace the part of the image erased by the Sprite
:RecallPic
:.I used conditionals because the boundary conditions are important
:.Replace with X+getKey(3)-getKey(2)→X if they aren't important.
:If getKey(3) and (X<92)
:X+1→X
:End
:If getKey(55) and (X<72)
:Pt-On(X,Y,Pic1+8
:End
:If getKey(2) and (X>2)
:X-1→X
:End
:If getKey(1) and (Y<60)
:Y+1→Y
:End
:If getKey(4) and (Y>2)
:Y-1→Y
:End
:End
.MOUSE
[101010FE10101000]->Pic1
While 1
.Store the screen to the back buffer
StorePic
.Display Sprite
Pt-On(X,Y,Pic1
DispGraph
.Erase Sprite
Pt-Change(X,Y,Pic1
.Replace the part of the image erased by the Sprite
RecallPic
.I used conditionals because the boundary conditions are important
.Replace with X+getKey(3)-getKey(2)->X if they aren't important.
Repeat getKey->Z
End
If Z=15
Goto 9
Else
If getKey(3) and (X<92)
X+1->X
End
If getKey(55) and (X<72)
Pt-On(X,Y,Pic1+8
End
If getKey(2) and (X>2)
X-1->X
End
If getKey(1) and (Y<60)
Y+1->Y
End
If getKey(4) and (Y>2)
Y-1->Y
End
End
End
Lbl 9
The one which is below was edited by me and is really really really slow. The above one is perfect and works really fine!

Any idea why? I know why (Else and GetKey) but how to fix? THX!

You said it yourself, the problem is the Repeat getKey→Z. Having that in the code will not let program execution advance until that getKey returns a value. When holding down the arrow keys, this will only return a value a few times per second, resulting in the mouse moving code only being reached a few times per second.

I see that you added it so you could press clear to jump out of it, so why not just use direct key input (e.g. getKey(15)) for the clear button as well as the arrow keys?

I see some potential relatively major optimizations. which code will you be using?

getKey(15) will equal 1 if the clear key is being held down and 0 if it isn't. That's all it does: return a value. If you want it to actually do something useful based on whether or not it (or any other key) is held down, you have to put it as the condition in an if statement and then put what you want it to do as the contents of the if statement, just like the other 5 if statements already in the code.

That should work, as long as you insert it into a suitable place in the code. Where did you try putting it?

Quote from: ScoutDavid on December 05, 2010, 10:31:29 am

Code: [Select]

If getKey(3) and (X<92)
X+1→X
End
If getKey(2) and (X>2)
X-1→X
End
If getKey(1) and (Y<60)
Y+1→Y
End
If getKey(4) and (Y>2)
Y-1→Y
End


could be

Code: [Select]

X<92 * getKey(3) -  (X>2 * getKey(2)) + X -> X

Y<60 * getKey(1) -  (Y>2 * getKey(4)) + Y -> Y

I think this gives a speed increase and lowers the byte size.
It should also make the game speed slightly more stable, although this is so small that that wouldn't be noticed here.

I don't think so. Multiplication by a non-constant is definitely one of the slowest things you can do.

Edit:
You could replace the multiplications with and in this case, because you are operating on two values that are 0 or 1.

.MOUSE
[101010FE10101000]->Pic1
While 1
.Store the screen to the back buffer
StorePic
.Display Sprite
Pt-On(X,Y,Pic1
DispGraph
.Erase Sprite
Pt-Change(X,Y,Pic1
.Replace the part of the image erased by the Sprite
RecallPic
.I used conditionals because the boundary conditions are important
.Replace with X+getKey(3)-getKey(2)→X if they aren't important.
If getKey(3) and (X<92)
X+1→X
End
If getKey(55) and (X<72)
Pt-On(X,Y,Pic1+8
End
If getKey(2) and (X>2)
X-1→X
End
If getKey(1) and (Y<60)
Y+1→Y
End
If getKey(4) and (Y>2)
Y-1→Y
End
If getKey(15)
Fix 4
Return
End
End

This works, why?

I have an idea of how to make mouse events now

return, while not part of a subroutine quits the program.

I always have fix 4 because i always use fix 5.

I know what Fix 5 does (concetane images and text), but not Fix 4