different sprite moves problem

[Nicknack]

i have created some codes which all uses different ways to retrieve the sprite position and i discovered that movesprite doesn't handle all those equally.
if you use spriteposint or spritex movesprite will floor the new position values (therefore moves the sprite in wrong direction), whereas spritepos and spritexint produces correct ones.
just click around, follow the sprite and tell me your thoughts about it

[Leginus]

Interesting discovery and it does the same here.
The saving fact is that although these are different, there isn't a need to use the different ones in a single scenario, but I guess you knew that and was just pointing the fact out that they are different.

Wow, don't I go on after a beer :-)

[zehlein]

Contrary to what the help file tells us (and what it's meant to be) SpriteX() seems to give back an integer value and SpriteXInt() the float value of the sprite's position. Alain did it wrong in his code obviously.
Besides this, the sprite is acting as one should expect, not moving to higher x or y positions, only moving to the lower ones if you retrieve the position as an integer.

[Nicknack]

i thought it would be something like this, but why moves it only with lower integer values?
does ppl handles them then as float again?

[zehlein]

If you use your debugger you can see pretty clearly what is happening let' say using SpritePosInt():

• If you tap the screen right of Mario:
  angle$ becomes something between 0 and 10. Only if angle$ is exactly 0 (you have to tap the screen at x=100) cos360(angle$) will become 1. All other values will result in values lesser 1.
  Therefore after the line
  x$+=cos360(angle$);
  x$ will be in most cases 110<x<111 !
  Now the MoveSprite() uses the integer value of the x$ only, the sprite will not move to x=111.
  And, on top of this, at the next GameProc-call SpritePosInt() will set back x$ to 110 exactly - it returns integer values! Off you go - Mario won't move right (again, except for the case you tap the screen exactly at x=110)!
• If you tap the screen left of Mario
  The x$-value becomes 109<x$<110. This will always move Mario to the left (x=109). After the next SpritPosInt()-call x$ is exactly 109 and if you tap left of Mario again, x$ becomes 108<x$<109. It will move left again.

Hope I could express myself clearly enough

Edit:
The simple

if (wParam$>x$)
  x$++;
else
  x$--;
end;

Is the better choice to deal with Mario here, except for the fact that the user would expect Mario to move left by tapping the screen at x=111 (he tapped in the left part of Mario's sprite!).
So the perfect solution would be

if (wParam$>(x$+SpriteWidth(sp$)/2))
  x$++;
else
  x$--;
end;

[Nicknack]

so in short, ppl floors the decimal values to get them as integer and therefore prefers most time the smaller position?
that would make sense, thanks for your great help
your other solutions might be only better if you don't care about straight lines as movement.