|Post 4 made on Friday August 17, 2007 at 08:02|
thanks for taking the time to test this - and also thanks for the compliments on the graphics ;-)
As for the controller / ball movement: that's, when there is too much to be calculated (if there are only 5 bricks left, everything runs really smoothly) - and, I fear, that my code is quite dirty. I am not too confident, that the script can be sped up significantly, though: Clean or dirty code, either way, up to 30 collision checks need to be made during one program cycle...
That's why I wanted to fiddle with the scheduler method to speed things up. But I really don't understand its purpose. Why all this try, catch, diagnostics? I don't understand it - all I want is to have this.process() looped, but I couldn't get it to work.
I checked the website of the Pong's author, but to no avail. I didn't even find the source code...
So, I keep working on this little game here.
Thank you again for your help, Lyndel.
TSU-9600, URC MX-3000, ProntoProNG TSU-7000