From: Diederick C. N. <dc...@gm...> - 2011-06-16 06:46:38
|
Dear all, I have not yet received any feedback on the below issue or on the patch that was sent before (I know you are busy John), so just wanted to bring these two points to your attention again. Best and thanks! Dee On Mon, Jun 13, 2011 at 12:23, Diederick C. Niehorster <dc...@gm...> wrote: > Dear All, > > There is another issue I have been thinking about in the patch: > FreeGLUT allows you to call glutFullScreen() on child windows > (original GLUT does not), but what are the semantics of that? > - a child window only exists inside its parent's client area > - a child window's coordinates are relative the the parent's > -> FreeGLUT currently (before and after my patch) resizes a child > window to the size of the whole monitor, which doesn't make sense. > -> fullscreen for a child window could instead mean resizing it to > cover its whole parent. But that wouldn't necessarily be very > fullscreen, right? and it probably wouldn't do what the user not > familiar with the nature of child windows expects. > > So maybe it is safer and more logical to disallow calling fullscreen > on a child window, as original GLUT does. Maybe, as FreeGLUT has > allowed this call before before, we should make calling glutFullScreen > on a child window a noop that simply displays a warning. > > What do you guys think? (In any case, I would say lets make this an > issue to look at after the patch I sent before has been vetted). > > Best, > Dee > |