Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!usc!polyslo!cosmos.acs.calpoly.edu!mdeale
From: mdeale@cosmos.acs.calpoly.edu (Myron Deale)
Newsgroups: comp.sys.next
Subject: Re: BreakApp
Message-ID: <13261@polyslo.CalPoly.EDU>
Date: 7 Aug 89 01:31:38 GMT
References: <13244@polyslo.CalPoly.EDU> <11148@polya.Stanford.EDU>
Sender: news@polyslo.CalPoly.EDU
Reply-To: mdeale@cosmos.acs.calpoly.edu.UUCP (Myron Deale)
Organization: ACS, Cal Poly, San Luis
Lines: 23

In article <11148@polya.Stanford.EDU> aozer@NeXT.com (Ali Ozer) writes:
>In article <13244@polyslo.CalPoly.EDU> Myron Deale writes:
>>  I'm just wondering if there's a fix for when the ball
>>goes to "hyper-velocity" and goes *through* the tiles rather than
>>bouncing them out.
>
>The fix would be to change the maximum y velocity in the BreakView.m
>file. The sources to BreakApp are in /NextDeveloper/Examples/BreakApp.
>I believe it'll be enough if you reduce the maximum velocity by two...
>
>Ali Ozer, NeXT Developer Support

   The velocity I don't mind. Gives ya' a little something to worry
about. But when you have "hyper-velocity" it is possible to aim for
a tile and have the ball go *through* it. Repeatedly. If the ball
can at least hit the tile there's the possibility of things slowing
down and the chance of completing the round. Otherwise you just have
to let the ball go by. Hopefully there are some remaining.

   ... sure is hard with the small paddle :)

-Myron
// disclaimer: i_speak_for_me_and_not_for_them