Quoting Noberasco Michele ([EMAIL PROTECTED]): > On Fri, 18 Jul 2003 12:29:00 +0200 > Denis Oliver Kropp <[EMAIL PROTECTED]> wrote: > > > The primary surface is an "API shortcut". You are already using the > > non-short version by getting the layer yourself. Also creating a > > primary surface is mainly useful for apps running normally fullscreen. > > I suggest to create a window on the layer instead of creating a > > primary surface. You can call GetSurface() on that window and the rest > > of your code doesn't need to change. > But qingy is (should be) a full screen app, and it needs windows. I use > the primary surface to draw a background image, so that all windows > created above it show this image in semi-trasparency. Do you know of a > better way to handle this?
In addition to creating windows on the primary layer you can set the background image. You can read through dfbg.c for an example, or simply check the API documentation for IDirectFBDisplayLayer::SetBackgroundMode(). > > > The call to primary->GetSize return wrong screen size (640x480 while > > > screen resolution is 1152x900), so all graphics in my app is the > > > wrong size/position. Any ideas? > > 640x480 is the default primary surface size in windowed mode. > Strange that on x86 this returns the framebuffer current resolution (and > thus magicall all is in the right place...). 640x480 is the first mode in the default /etc/fb.modes of Debian. Check IDirectFBDisplayLayer::SetConfiguration() or the "mode=" option. -- 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.
