Path: utzoo!utgpu!watmath!att!ucbvax!agate!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: BreakApp
Message-ID: <11152@polya.Stanford.EDU>
Date: 7 Aug 89 14:44:43 GMT
References: <13244@polyslo.CalPoly.EDU> <11148@polya.Stanford.EDU> <13261@polyslo.CalPoly.EDU>
Sender: Ali T. Ozer <ali@Polya.Stanford.EDU>
Reply-To: aozer@NeXT.com (Ali Ozer)
Organization: .
Lines: 15

In article <13261@polyslo.CalPoly.EDU> Myron Deale writes:
>In article <11148@polya.Stanford.EDU> aozer@NeXT.com (Ali Ozer) writes:
>>The fix would be to change the maximum y velocity in the BreakView.m
>>file.
>
>   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. 

The reason the ball goes through the tile is because the super cheap
implementation allows the ball to skip over the tile when its y-velocity
is at the maximum. If you set the maximum y velocity a little lower, it
won't go through the tiles. 

Ali