On 12/4/05, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > Quoting Mike Emmel: > > Thanks I was seeing this myself but had not chased it down. > > > > I've been wondering if we need access to some of the global locks i.e > > the window manager > > in the gtk port ? My opinion right now is no DirectFB should do the right > > thing. > > Yes, applications should not be responsible for these locks. > > But some higher level locks like "window stack update freeze" > might be handy for e.g. moving and resizing a window or showing > or moving several windows at once. >
Hmm I'm not sure we ever get into this situation in normal usage but for doing something like the apple all window view ( I forget what they call it it ) would be useful. I'm sure there must be other cases where a stack freeze would be useful. Actually one big need is to lock one window as always above another so a callback to application level library to prevent certain operations would be nice. I'd also like to manager the window decorations via the gtk themes which means that for window manager that have a decoration window I need callbacks to manage those. I'd rather register this way with the window manager then have gtk have its own directfb window manager. In any case the directfb window managers are fairly strait forward so when we get to the point that these are burning issues I'll review. Mike > -- > Best regards, > Denis Oliver Kropp > > .------------------------------------------. > | DirectFB - Hardware accelerated graphics | > | http://www.directfb.org/ | > "------------------------------------------" > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
