Hi Manju, I would not describe the screen as a desktop. The screen maps closer to a multi-monitor system that might support different hardware blended display layer output (or the same), each with potentially multiple signals/outputs.
>1. If a screen is like a desktop, the modes and resolutions >should be an attribute of the screen. In directFb I see them >as methods of the topmost object IDirecFB. How can I set >independent resolutions to different screens? The IDirectFB::EnumVideoModes and SetVideoMode APIs are dated IMHO and I believe may have roots in a simplier desktop usage model (and other APIs like DirectDraw) in which it was sufficient to simply identify the mode's width, height and bits-per-pixel and look-up the first matching mode in the list of those supported in the frame buffer driver list. Instead, use the IDirectFBScreen::SetEncoderConfiguration function to configure individual encoders (either DirectFB 1.0.1 or preferably 1.1 since it has needed improvements for ED and HD display modes). It allows a much more complete description of the required display mode to be specified. In the DirectFB drivers I'm developing for CE usage, I am NOT reporting support for any display modes-- thus EnumVideoModes/SetVideoMode are not very useful. :) >2. How can I setup an extended desktop scenario? Use IDirectFBScreen::SetEncoderConfiguration and IDirectFBScreeen:SetMixerConfiguration (provider that your drivers support encoders and mixers). Regards, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation The views expressed above are my own and not those of Intel _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
