Re: [Iris-devel] what about this (can a subject get more meaningless then this ?)

[foser]

Cédric Delfosse wrote:
> Yes, in openGL you can specify the cube of the scene that will be
> rendered. I think this is it, in iris.c:
>
> glFrustum (-1, 1, -1.5, 1, 1.5, 10);

Oki, ill fool around with that, see if i can get it right. I suppose a 
bigger cube will lower performance a bit.

> > 2. Energy indentifier can be removed, Knot used it for a while. It now 
> > uses loudness (works much better imo). Or is somebody gonna/still 
> > us(e/ing) it ?
>
>
> I don't use it !

Then consider it gone.

> I have changed the option "fullscreen", that is now "start on
> fullscreen".
> This means when the plugin is started, it will go fullscreen only if the
> option is set.

Oh ok. I remember i did it somewhat different and when i used the 
fullscreen option in the menu i couldnt switch back when pressing f, but 
thats done better now.

> Please take a look at the description fields of the themes. Sometimes, I
> don't know what to say !
> Oh, and where did you steal the code for the knot theme ? Did you ask
> the author his permission for the inclusion ?

It's GPL anyway, but i still asked him and it was ok for me to use it, 
it's maybe nicer to name him somewhere. I'll have a look at the naming 
fields and add it somewhere.

> I'd like to release iris 0.10. I think the cvs is in a good shape. What
> do you think ?

I think it's fine mostly, altough theres 2 problems i know of. One is a 
segfault on disabling and then re-enabling the plugin here. It is 
reproducible here, but i use usually agressive optimalisations in all my 
compilations. That might have to do with it.

Second is still a problem with theme initialisations after destroying 
and creating a window (on fullscreen switch or startup). The depth 
calculations are incorrect and it always starts out non-blended whatever 
the config choices are. I'll have a look at that too, but what i recall 
from last time i checked that it isn't really easy to solve.

If the segfaults turn out to be a local problem, the 2nd bug is minor 
and it isn't a showstopper imo. So wrap it up in some nice paper and 
give it to the world :)

- foser