On Sat, 2010-05-08 at 11:50 +0530, Melwyn Lobo wrote: > > Using DSCAPS_VIDEO, you force DirectFB to allocate from framebuffer > > memory. Otherwise DFB might decide to use system memory, via simple > > malloc(). > In the case of multiple DFB applications where all the surfaces are > created as primary and with video caps...would it not lead to > flikering updates to the screen > as all window surfaces are created on fb.
For full screen apps, you can transparently force them into a window using --dfb:force-windowed, so the app will believe it's running full screen, but in fact it will end up inside a DirectFB window (as the option suggests :-) Otherwise, the app started last will be 'on top' of all the existing apps, hiding/suspending them. > > Using fusion, you can run multiple independent DirectFB applications at > > the same time. The same holds true for QT applications when QT uses DFB > > as a back end. > Does fusion also allocate memory for surfaces... Not really, fusion is just an IPC mechanism. > is it true that fusion > shared memory is mmaped at the same location > in each applications address spaces Yes. Cheers, Andre' _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
