> 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. 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
- RE: gcc vs anything else Todd Christensen
- Re: gcc vs anything else Tom Zerucha
- Re: gcc vs anything else Michael Obenland
- Re: gcc vs anything else Eric Cloninger
- Re: gcc vs anything else Ralf Beckers
- Re: gcc vs anything else Nathan J. Williams
- Re: gcc vs anything else Kenneth Albanowski
- Re: gcc vs anything else Nathan J. Williams
- Re: gcc vs anything else Chris Antos
- Re: gcc vs anything else Kenneth Albanowski
- Re: gcc vs anything else Aaron Ardiri
- Re: gcc vs anything else Aaron Ardiri
- Re: gcc vs anything else Aaron Ardiri
- RE: gcc vs anything else Fawcett, Mitch
- Re: gcc vs anything else Dave Lippincott
- Re: gcc vs anything else Murray Dowling
- Re: gcc vs anything else Aaron Ardiri
- Re: gcc vs anything else Michael S. Davis
- Re: gcc vs anything else Michael S. Davis
- Re: gcc vs anything else Jun-Kiat Lam
- RE: gcc vs anything else Mike Pellegrino
