On Thu, 8 Apr 1999, Aaron Ardiri wrote:
> > On Wed, 7 Apr 1999, Aaron Ardiri wrote:
> >
> > > > None of these errors seemed sufficient to cause a problem in the
> > > > double-buffering code though - unless GCC was doing something way weird.
> > >
> > > ok.. i think this is a gcc problem.
> >
> > I think it is because you are trying to free something you didn't
> > allocate.
> >
> > Why are you using WinDeleteWindow instead of WinRemoveWindow?
>
> ok.. maybe that is the problem with "freeing it".
>
> but it still does not explain why the double buffering does not
> work.
i just looked at the API docs.
WinRemoveWindow
---------------
Purpose: Remove the specified window from the window list.
...
Comments: Doesn't free the memory used by the window.
nope.. that aint going to work.. thats for sure. from memory i
remember the HardBall demo using WinDeleteWindow - and NOT
WinRemoveWindow.
gcc has screwed up big time.
any gcc people here? i want the source.. i fix this shit
myself. - i bet they overlooked some of the asm("")
implementations..
cheers.
az
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 352 8192 A/H: +46 26 10 16 11
