Hi, [EMAIL PROTECTED] writes:
> As per my last message, I am trying to use the new Matrox G400 CRTC2 > features of DirectFB. I have a GTK application that I built for my > on-screen-display, and it used to work fine when I did all the > mucking about redirecting CRTCs and the sort with matroxset. Now I > want to use it with the native CRTC2 support in DirectFB. Is this > possible? > > The homework I have done so far is to determine (by looking at dfbtv) > that when the DFB instance is created, it grabs display layer 2: > > dfb->GetDisplayLayer( dfb, 2, &crtc2 ); hardcoding the value to 2 is probably even worse than hardcoding it to DLID_PRIMARY. I'd suggest you call DirectFB::EnumDisplayLayers and determine the layer to use by looking at the type member of the DFBDisplayLayerDescription. This way you should be able to write software that will also work on hardware that offers only a single display layer. > However DirectFB-GTK grabs layer 0: > > #define DLID_PRIMARY 0x00 > ... > ret = DirectFB->GetDisplayLayer (DirectFB, DLID_PRIMARY, &DisplayLayer); > > This is hardcoded in the GDK initialization for the DirectFB backend. yes, GTK+-DirectFB-2.0 doesn't handle multiple layers yet. I plan to add support for multiple layers when doing the port to GTK+-2.2. > Am I correct so far? (I hope I am because I am going to change > DLID_PRIMARY in the GetDisplayLayer() call to 2 in my DirectFB-GTK > tree and rebuild) as mentioned above, this is rather ugly but you should get away it... Salut, Sven -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
