From: Holger L. <de...@la...> - 2006-10-08 12:27:18
|
Hi, On Wednesday 23 August 2006 06:30, David Yoder wrote: > Indeed the problem was there. tux_frame was not getting set for the path > through the code in which <esc> is pressed before animation is done. I ju= st > initialized tux_frame. Hm. You only saw this problem in the old tuxtype package (1.0.5 from dapper= ),=20 but not with the 1.5.4 from testing? Cause I know I have seen this problem= =20 there, even though your fix also is there. > diff -urN tuxtype/branches/tuxtype1/tuxtype/graphics.c > tuxtype-dmysegfault/branches/tuxtype1/tuxtype/graphics.c > --- tuxtype/branches/tuxtype1/tuxtype/graphics.c 2006-08-22 23:06: > 37.000000000 -0500 > +++ tuxtype-dmysegfault/branches/tuxtype1/tuxtype/graphics.c 2006-08-22 > 23:06:13.000000000 -0500 > @@ -329,7 +329,7 @@ > back_h; > int i, > j, > - tux_frame; > + tux_frame =3D 1; > int x =3D 0; > int y =3D 0; > int dirx =3D 1; This has been done in tuxtype/titlescreen.c now. $ grep tux_frame tuxtype/trunk/tuxtype/titlescreen.c=20 int i, j, tux_frame =3D 0; tux_frame =3D 0; case 0: tux_frame =3D 1; break; case TUX1: tux_frame =3D 2; break; case TUX2: tux_frame =3D 3; break; case TUX3: tux_frame =3D 4; break; case TUX4: tux_frame =3D 3; break; case TUX5: tux_frame =3D 2; break; There must be something else triggering the bug,=20 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D217448 regards, Holger |