openglean-devel

[openglean-devel]Re: A question about menu windows

[Richard R. <sf...@ol...>]

> Is there a good reason not to allow input callbacks for menu windows
> and delegate everything to the parent window?

I'm not sure that I understand your question, Varol.

Possibly I'm just not fully awake this morning.  However, I'll try to
answer it:

Mouse and keyboard events should already be delegated to the parent
window.  Those events cannot be meaningfully registered directly on
the menu window because the parent must handle them.

The reason that the events get pushed from the menu window to the parent
is because in some cases it seems to be *forced* to be that way, at the
window system level.  WIN32 behaves one way, and the UNIX_X11 branch
of OpenGLEAN varies it behavior with your window manager.

I would prefer to see the individual windows handle the callbacks
just like non-menu top-level windows.  I don't know when I might
get around to trying to address this, but patches for it would
be appreciated.  (^&

(If you're at all interested: The stay-on-top window support has
code for determining the current window manager.  See near the
bottom of .../src/window.c in the main OpenGLEAN library.)

-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/

Re: [openglean-devel]Re: A question about menu windows

[Richard R. <sf...@ol...>]

On Thu, Sep 15, 2005 at 12:04:03PM -0500, Richard Rauch wrote:
 [...]
> window system level.  WIN32 behaves one way, and the UNIX_X11 branch
> of OpenGLEAN varies it behavior with your window manager.

Um, just to pick at nits, this isn't quite clear:

OpenGLEAN tries (fairly well, I think) to give the same behavior
on all WIN32 and UNIX_X11 systems.  In the case of menu windows,
the current behavior seemed to be the strongest common behavior.
There may be consistency problems, though, and there may be a
better way to address this.

-- 
  "I probably don't know what I'm talking about."  http://www.olib.org/~rkr/