0 Members and 6 Guests are viewing this topic.
idk if it's possible or not, but can you add a "hittest" for object-object(sprites)?
In other news, Frey continues kicking unprecedented levels of ass.
Can there be an option to make pxl-test() return a one instead of zero when it is out of bounds?
Quote from: Freyaday on December 16, 2011, 12:25:45 amCan there be an option to make pxl-test() return a one instead of zero when it is out of bounds?Frey wouldn't it just be easier to check if the coordinates are outside of the bounds of the screen first?I'm in favor of a really optimized scrolling tilemapper routine, but I'd like to see some more of these agressive ops
Maybe auto-backup for libraries.
Quote from: leafiness0 on December 16, 2011, 12:40:43 amQuote from: Freyaday on December 16, 2011, 12:25:45 amCan there be an option to make pxl-test() return a one instead of zero when it is out of bounds?Frey wouldn't it just be easier to check if the coordinates are outside of the bounds of the screen first?I'm in favor of a really optimized scrolling tilemapper routine, but I'd like to see some more of these agressive ops Bounds checking is built in to the routine, and it'd be a trivial matter to change it from returning a 0 to returning a 1
What about support for the crystal timers?