0 Members and 2 Guests are viewing this topic.
I don't hate you. Nah that aside, I kinda forgot about it because I play 2048 when bored and I don't bring my calcs everywhere. So I play on my phone.also undo button
Everyone who's complaining about the slow anims: This is why I need optimization. I mean, I'm doing a lot of calculations when the moves occur. I'm using grayscale. I'm doing 3 byte scores. My graphics are 15x15 Bitmaps. There has to be a Game Over check and Win check after every move. There are probably some snippets of code I'm not sure I need, like a use of the abs() token somewhere in the animations. What do you expect in terms of instantaneosity?
.Just so we're clear, GDB1 is:.0,16,32,48,0,16,32,48,0,16,32,48,0,16,32,48,0,0,0,0,16,16,16,16,32,32,32,32,48,48,48,48.That should clear some stuff up..Lbl ANIMCopy(GDB1,L1+48,32)0->[r3]For(16)^^rabs([r3]-{[r3]+32+L1})->{[r3]+32+L1}[r3]++EndFor(4)^^r15For(16)^^rRect(->[r3]^4*16,[r3]/4*16,15,)^^r[r3]-1EndFor(16)^^r[r3]+48+L1->[r4][r4]+16->[r5]If {[r3]+16+L1}WRect({[r4]},{[r5]},15,)^^rBitmap({[r4]},{[r5]},{[r3]+16+L1}-1*32+Pic1)End!If K{[r5]}+({[r3]+32+L1})->{[r5]}Else!If K-1{[r4]}-({[r3]+32+L1}*4)->{[r4]}Else!If K-2{[r4]}+({[r3]+32+L1}*4)->{[r4]}Else{[r5]}-({[r3]+32+L1})->{[r5]}End[r3]++EndDispGraph^^rWRect(0,,63,)End
Quote from: Streetwalrus on June 07, 2014, 06:50:15 pmI don't hate you. Nah that aside, I kinda forgot about it because I play 2048 when bored and I don't bring my calcs everywhere. So I play on my phone.also undo buttonUNDO BUTTON? UNDO BUTTON? WE DON'T NEED NO STINKIN' UNDO BUTTONS! JWinslow23: You hit the end of the craze. Personally, I would use your version, but I don't have a 84.