Quoting Daniel Laird: > Hi all, > > I am working on DirectFB in a product. > We currently allow the user to change from PAL-NTSC via the > SetEncoderConfig function. > > When this change takes place we change all of the Display Layer properties > to the new resolution > (720*576). > This is done internally ie from within our SetConfig function of our Enoder > driver. > > This works fine. However, all of the surfaces that are created on the > display layers still think that they are 720*576 not 720*480. This means > that when they start to draw we get an out of range error. > > What are other people doing when they change to NTSC? > Is there a way to change all of the Display layers AND surfaces internally > from our driver? > If we do this how will this effect an application using the library as they > to need to be informed of Surface changes. > > Is the preferred method to change all of the Display layers internally and > inform users of DirectFB on our hardware that after a call to > SetEncoderConfig(NTSC) that they have to release, and create all surfaces > or is there a better way?
The size of a display layer is independent of the screen size. Applications have to reconfigure the layer using SetConfiguration() and GetSurface() after releasing the old one. Changing the layer(s) and surface(s) internally/implicitly would be possible, but it should be a special option in the public API and would require some efforts to cope with the side effects etc. -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" _______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
