Hi Ravi.
You should consider windows as being programmed "on top of" layers.
This means that in theory you can program windows yourself, using the
layer and surface interfaces.
The window implementation will benefit from hardware acceleration and is
programmed optimally, given one or two assumptions. One of these
assumptions is that each window has by default a surface from system
(not video) memory. Think here of windows that will be slowly filled by
the UI and then quickly blitted to the screen. If you have separate
video/system memory you can experiment with this. You can also do some
dumping and look at the timestamps to get an idea of where your system
time is going to.
So yes, you can implement windows yourself on top of the primary
surface, but I doubt that it will result in a quicker system, given a
correct tweaking of DirectFB.
Greets
Niels
Ravi Karmarkar wrote:
Hi All,
From what I understand I can either use windows to build my GUI or
blit to the primary surface directly.
There seem to be some advantages of using windows like the 'z order'
is maintained by DFB etc. However, things seem to be pretty slow when
using windows, especially if they are big in size.
Is there a distinct speed advantage if I use the primary surface
directly? Basically can everything that can be done using windows be
done without them?
Please give me some pointers to choose between the two methods.
Thanks and regards,
Ravi Karmarkar
------------------------------------------------------------------------
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
