[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Win32 3D build Sep 15th

From: Holger
Subject: Re: [Bug-gnubg] Win32 3D build Sep 15th
Date: Mon, 15 Sep 2003 19:49:21 +0200

At 19:37 15.09.2003 +0200, Jim Segrave wrote:
On Mon 15 Sep 2003 (19:26 +0200), Holger wrote:
> At 18:40 15.09.2003 +0200, Jim Segrave wrote:
> >I have no idea why there's 44, 35, 99, you name it. It's a nightmare
> >of fixed constants which I assume are related to board dimensions.
> Yes, in render.c it's very difficult to find out where the numbers came
> from. So here I only replaced a few values with defines that were more or
> less obvious. But this should have made no impact since I didn't change the
> values, but one.
> Maybe this line may turn out as the culprit (had a value od 81):
>      FillArea( puch, nStride, prd->nSize * BOARD_WIDTH, prd->nSize *
> BOARD_HEIGHT /*81?*/,

That probably needs to be (BOARD_HEIGHT - 1). I think 44 is
(BOARD_HEIGHT / 2 + 3), 35 might be (BOARD_HEIGHT / - 6), 99 is
probably (BOARD_WIDTH - 9) etc. since there seems to be 3 bytes per

I'll change it back to 81 (that is, BOARD_HEIGHT - 1). Hopefully that's already it.

point. But overall, it needs whoever coded this to put in values
defined in terms of the fundamental dimensions. Otherwise we'd be just

Who knows about this?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]