On Mon, Nov 04, 2002 at 07:40:04PM +0100, Sven Neumann wrote: > Hi, Hi.
> hardcoding the value to 2 is probably even worse than hardcoding it to > DLID_PRIMARY. As a general soltuion, yes I agree. But my immediate need is to get my GTK app. working again. Once I have that happening, we can look at the general solution. > 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. Right. The better general solution. > 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. OK. > as mentioned above, this is rather ugly but you should get away it... Actually, this did not work. I only wound up with the following errors: (chooser2:25094): Gdk-DirectFB-WARNING **: unsupported pixelformat (chooser2:25094): GLib-GObject-WARNING **: invalid cast from (NULL) pointer to `GdkVisual' Gdk-DirectFB-ERROR **: file gdkvisual-directfb.c: line 178 (_gdk_visual_init): assertion failed: (system_visual) aborting... (!) ---> CAUGHT SIGNAL 6 <--- Aborted (core dumped) I will have to dig deeper, but any hints you could provide would be much appreciated. Thanx, b. -- Brian J. Murrell
msg01002/pgp00000.pgp
Description: PGP signature
