On 6/11/06, Ville Syrjälä <[EMAIL PROTECTED]> wrote: > On Sat, Jun 10, 2006 at 08:28:11PM -0700, Mike Emmel wrote: > > On 6/10/06, Ville Syrjälä <[EMAIL PROTECTED]> wrote: > > > On Sat, Jun 10, 2006 at 12:55:30PM -0700, Mike Emmel wrote: > > > > Can you show me how to be and administrative process I don't know about > > > > that. > > > > > > layer->SetCooperativeLevel( layer, DLSCL_ADMINISTRATIVE ); > > > > I got that part I guess my question is whats the difference between this and > > shared since I've generally seen code thats sets the layer as shared. > > Basically I don't understand the difference between admin and shared. > > I guess the difference is that an administrative proces must manipulate > windows that are used by other processes. The current XDirectFB server > is an administreative process for example. > Okay got it now. I think I just need to do this and patch that code to check for administrative also. I think this might be a problem in a few places. I'll watch since in general these check should be shared || admin.
> > > > Its the wm so it fits the bill also since its loaded as a shared lib > > > > its the root process. > > > > > > So the wm is both a shared lib and a process? > > > > > No its a shared lib loaded as the driver by master I mean its loaded > > into the root > > directfb process. > > Normal wm modules (and other modules too) are loaded into every process. > Are you doing something different? > Your right but thats not quite the right design in the shared case we need a global window manager so I need to split it so there is only one root wm. I think the code is there for handling multiple processes the second wm would just attach and defer to the root one. I need to read through some if this to make sure there exists only one "real" wm. Anyway I'll fix this when I get to it. I think it should be the first wm loaded sees all processes windows. The rest just see there own and shared ones. > I'm wondering why you are trying to use the public IDirectFBDisplayLayer > API in the wm? You should probaly just call the internal functions > directly. > I'm porting metacity over its the gtk/x11 wm so I need the interfaces to drive gtk. Actually it turns out to be easier since I get all the event handling for free. If you have application code that you want to make part of the wm this approach makes it trivial. Mike > -- > Ville Syrjälä > [EMAIL PROTECTED] > http://www.sci.fi/~syrjala/ > _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
