I'm writing a GUI using IDirectDBWindows for all of my buttons. I'm running this application on an embedded platform, and using so many windows (~10 + a parent window) makes it impossible to do transition animations between screens. I'd like to be able to "flick" between screens specifically. When I wrote all of this up using simple surfaces and blitting operations, the transitional effects worked smoothly. I realize that the overhead that I have added with the IDirectFBWindows is causing the performance hit, but I'm not prepared to give up just yet... unless this is just not an advisable way of doing things. I rather enjoy the cleaner event loop over the touchscreen zone filtering that I had to do when I wasn't using windows.
If I could dump the current contents of the visible display layer to a surface, then I could scroll a single surface for the animation and replace it with the windows once the animation loop has completed. I can't find an efficient way to dump the display layer contents though. Does anyone have any ideas that I can try? I would rather not have to blit each window surface to the dummy surface manually, but that's the only option that I can think of that is supported. Also... If I'm going about this completely wrong conceptually, I'd love to hear about that as well. The sooner I'm on the right track the better. -- View this message in context: http://old.nabble.com/Dump-layer-contents-to-a-surface-tp30134212p30134212.html Sent from the DirectFB Users mailing list archive at Nabble.com. _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
