Quote from: Deep Thought on September 29, 2012, 07:16:30 pm

Quote from: Sorunome on September 29, 2012, 04:38:37 pm

Oh, nice idea But wouldn't it also work without the pause?

It doesn't for me. Pause 8 seems to be the smallest pause that allows the code to work correctly.

why does it need pause?

Otherwise it records zero once in a while even if a key is held down, because the keypad doesn't update fast enough.

A+B+C+D+E+F+G+H+I+J->K (21 bytes) compiles to 71 bytes.  Pt-On(A,B,C) (7 bytes) compiles to 146 bytes.  Some routines are bigger than others when compiled, using a couple larger routines can make the compiled program huge, even if your source seems small, while using a ton of smaller routines can keep the size down.

So Rect is 112 bytes larger than pt-on? Wow, that's huge. That means that I can save 112 bytes by using Pt-On for my paddle!

Oh... that makes more sense.
I need Rect for something else anyways, so I don't need to change anything.

Do you have any ideas on how to do slow-motion? I need something that slows the ball's movement, but not the timer or the paddle. I can't change its velocity; it won't land and bounce properly if I do - that's the cost of simulating gravity more accurately. And Pause doesn't work 'cause it slows everything down. I'm stuck.

No, 'cause the paddle and timer are processed in the main loop. I could possibly make a separate engine for the ball and tell it to run X number of times...
But then the default non slow-motion speed would be at least 2 times as fast as it is now.
And that's a lot of work to do...
Any other ideas?

What you can do is add a timer for just the ball. Normally it can be set at, say 1, meaning that every time it reaches 0 (meaning every frame) you move the paddle. Later when you want slow motion, you can change the default delay to 2 or 3 so that it waits 2 or 3 frames before doing anything. If you want it to move just a little slower than everything else, set the timer to, say, 5, and run your routine to move the ball every time you update the timer EXCEPT when you reach 0. For every 5 frames that your paddle runs, the ball will be updated 4 times.

EDIT: something i do in asm all the time is use a counter and when it is divisible by 2/4/8/16 do something:
ld hl,timer
inc (hl)
ld a,(hl)
and $7 ;%111
ret z ;if bottom-most bits are 0, (meaning divisible by don't update the ball.

if a = 0 it means that it is divisible by 8, it's really quick. Doing modulus 3/some other complicated number might be a bit more slow and take up more space. You could use and $3, and $1, or even and $15 depending on how much of a delay you want.

Added slowmo (infinite for now), reordered some code, made the ABOUT, and fixed the 2nd issue. BOUNCE and BOUNCSRC have been updated on my 1st post.
I would've had this sooner, but RAM clears came. I had FOUR RAM CLEARS this week, each one restarting my progress. ARGGH.
3 bugs left: ball randomly deciding to skip, ball breaking the wall (less common occurrence now), and the time meter residue.

So what's wrong with my time meter? Here's what I've got:
:RectI(76,12,8,50)^r
:Rect(76,62-(T*2/15),8,T*2/15)^r
T is the amount of time left. I can't find the problem.

Optimized a few bytes.