I think I begin to understand.  It sounds like you are asking that "freeglut" set the current window to the window being destroyed when the window destroy callback is called.  On some further thought, the behaviour of GLUT is irrelevant here since GLUT doesn't have a window destroy callback.  Is this right?

John F. Fay

-----Original Message-----
From: Kenny Tilton [mailto:ktilton@nyc.rr.com]
Sent: Saturday, January 04, 2003 12:04 AM
To: freeglut-developer@lists.sourceforge.net
Subject: Re: [Freeglut-developer] Destroy callback set-up OK?

Fay John F Contr AAC/WMG wrote:
> I'm not completely sure what the problem is but let me take a stab at it
> anyway.
> The destroy callback is specific to the window; each window has its own
> destroy callback.  It is up to the application to determine which window
> is being destroyed when the callback is being called; probably the
> simplest way to do this (if it is necessary) is to have a separate
> destroy callback for each window.  If you have a bunch of windows with
> the same destroy callback, it is most likely that the exact identity of
> the window doesn't really matter.

Now it is my turn to be confused. In an OO world, it is quite common for
all instances to share the same code. In C++ I have "this", in smalltalk
I have "self", with glut I have nothing. (except I have already changed
my source to set the window before calling the destroy callback.)
Because when destroy is called on window 2 out of a possible 1, 2, or 3,
I need to clean up precisely window 2, not the others.


  kenny tilton
  clinisys, inc
"Cells let us walk, talk, think, make love and realize
  the bath water is cold." -- Lorraine Lee Cudmore

This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
Freeglut-developer mailing list