Quoting Sven Neumann ([EMAIL PROTECTED]): > Hi, > > I think we should add InputOnly windows to DirectFB. These would be > windows that have no surface but get events and can be used to grab > the pointer or keyboard. Basically the opposite of DWOP_GHOST. I'm > however not sure if it makes sense to make this a DFBWindowOption. > Window options may be altered during the lifetime of a window and this > could become a little tricky for InputOnly windows. So it looks like > it should be a DFBWindowCapability then, but how should we call it? > > DWCAPS_NOSURFACE, DWCAPS_NO_SURFACE, > DWCAPS_INPUTONLY, DWCAPS_INPUT_ONLY, ...?
DWCAPS_INPUTONLY sounds nice and familiar. > BTW, what is the purpose of DWCAPS_ALL? All *_ALL values are for sanity checks. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
