Re: [Libvisual-devel] SDL and openGL plugin issues.

[Vitaly V. B. <vit...@uk...>]

On Mon, 05 Jul 2004 23:36:33 +0200
Dennis Smit <sy...@yo...> wrote:

> On Tue, 2004-07-06 at 00:02 +0300, Vitaly V. Bursov wrote:
> > On Mon, 05 Jul 2004 21:54:47 +0200
> > Dennis Smit <sy...@yo...> wrote:
> > 
> > > 
> > > Vitaly,
> > > 
> > > If you have some time could you look into the following:
> > > at: http://libvisual.sourceforge.net/LIBVISUAL_TODO
> > > 
> > > * Fixes in some GL plugins that show odd behavior after another GL
> > >   plugin has been running (better state setting). (everyone!!!)
> > Yes, I've already seen this, tried to reproduce this and failed.
> > And I thought it was fixed...
> > 
> > > This is tiresome to debug but some GL plugins show up really odd
> > > after another had run before (in the same execution) using
> > > plugin switches. This is probably easier to monitor when you
> > > adapt the xmms plugin to only show GL plugins and show them
> > > randomly...
> > Now I see. :) Indeed, this is due to settings left by prev. plugin.
> > 
> > Even worse, If a plugin allocates, say, a (large ;) texture and does
> > not release it during cleanup, texture will still reside in video
> > memory. Just like with madspin plugin: there is glGenTextures()
> > call and no glDeleteTextures(). The same will be with other data
> > like lists.
> 
> Would you mind to clean this kind of things up anyway if I gave
> you CVS access to libvisual CVS ?
Sure.
SF's anon cvs isn't working again....
My SF login: vitalyvb

> > Looks like the only way to reset it nicely (everything is set to
> > defaults in any condition on any hw/sw) is to delete GL context
> > and create a new one.
> > 
> > And here goes a problem with SDL. To make it work right now,
> > you can destroy and create whole window or render surface in
> > SDL words. This is a bad behavior... Each plugin change (well,
> > gl-to-gl at least) the window will be recreated.
> 
> Yeah that is totally bummer, but if that is the only way for now...
glPush* / glPop functions can also be used but it will have slight
side effect like making stacks 1-entry shorter. And I am not sure
if everything can be saved/restored..

> > Another way to solve this problem is to use CVS version of SDL
> > in 1.3 branch. Pros and cons are pretty obvious. Does
> > anybody know then 1.3.0 will be released???
> 
> For libvisual-xmms we can't use SDL 1.3. SDL 1.3 is a must tho if it's
> not just only because off the offscreen buffers...
Hmm.... I was wrong. Current CVS version won't help here. They do not
create more contexts...

/*
 * Create a render target with the given size and attributes.
...
 * Currently this function does not create a new OpenGL context.
...
 */
extern DECLSPEC SDL_RenderTarget * SDLCALL SDL_GL_CreateRenderTarget ...


> Alright, thanks a lot tho for the comment, it really cleared
> things up!
My pleasure :)

-- 
Vitaly
GPG Key ID: F95A23B9