Hi, Bill Hayden <[EMAIL PROTECTED]> writes:
> This is part-rant, part-question, so please bear with me. > > I seem to be having a hard time getting started with DirectFB due to a > general lack of documentation and examples. (Yes, I've looked at all > the sample code, tutorials, and docs on the web site) I keep getting > hit with undocumented gotchas like the mouse cursor being unavailble > if you are in fullscreen mode. (Why?) If the sample code, such as > df_window.c, were documented with not just what it is doing, but why > it's doing it that way as opposed to another way, I don't know how > many days that would have saved me. we will happily accept your contributions to the documentation. > When I used SetCooperativeMode(FULLSCREEN) or (EXCLUSIVE), everything > drew fine but I had no cursor. When I took that line out, I got a > cursor, but the drawing was confined to a 640x480 surface in the > middle of the screen regardless of what I size I asked for. I believe > this is related to creating the main surface with DSCAPS_PRIMARY. If > I remove the DSCAPS_PRIMARY flag from the surface description, then > the surface is created at the right size but nothing draws at all to > the screen. Aaaargh if you just create a surface which is not the primary and not a window surface, you get an offscreen surface. I have no idea why your surface is not created the size of the primary layer. Actually it should be sufficient to set the capabilities to DSCAPS_PRIMARY and not specify the size. You are not creating a new surface here, you only retrieve an interface to the primary surface. It's size is already determined by the size of the display layer. Salut, Sven -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
