You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a feature request. I'm not experienced with java so I dont know if there are any implications to this.
Currently the arguments: x, y, originX, originY are accepted as int. Their immediate use inside of SpriteBatch .draw have them become float. If working in a space smaller then the actual pixel size of the screen, one might want to pass float values instead. Even if working solely with int, it seems java is not partial to an argument being cast as (int) when it requires (float) so it seems like a win-win
Will change in the next release (this weekend probably). Spritebatch was originally designed to be used with integer viewports. Given that box2d has a different worldscale i might as well change this. Note however that text will be all fucked up when drawn at none integer positions. So don't complain afterwards :)
From dasac...@gmail.com on June 17, 2010 05:04:54
This is a feature request. I'm not experienced with java so I dont know if there are any implications to this.
Currently the arguments: x, y, originX, originY are accepted as int. Their immediate use inside of SpriteBatch .draw have them become float. If working in a space smaller then the actual pixel size of the screen, one might want to pass float values instead. Even if working solely with int, it seems java is not partial to an argument being cast as (int) when it requires (float) so it seems like a win-win
Original issue: http://code.google.com/p/libgdx/issues/detail?id=9
The text was updated successfully, but these errors were encountered: