> On Tue, 21 Jan 2003, Christoph Egger wrote: > > How about using the memory target within libggi's kgi-target, when the > > application runs in background? > > That's basically what I mean.
Then you were not precisely enough. By using the word "offscreen", every- body thought, you mean an offscreen area of the onboard framebuffer... > > [...] > > > The big question is, if this will still work, once libggiovl becomes > useable > > and the GGI apps requests overlay resources such as hw-sprites and/or > > YUV-viewports... > > hw-sprites, I guess, would still be accessed trough an API, right? Hence > when the visual is not visible just update the internal sprites' state, > don't actually display them. The same goes for the YUV overlay: redirect > it to a memory target. When the visual become visible again then refresh > the display with the content of the various buffers and the sprites. That sounds a good idea. But then a) the memory-target must be extended to "support" overlay resources and b) the GGI application should be notified somehow, so that the GGI app can stop wasting CPU time with decoding a video, for example, when it knows that the result (the decoded video) gets no longer displayed... -- CU, Christoph Egger E-Mail: [EMAIL PROTECTED] +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
