Heh. How did it come I didn't notice this email before? Sorry.
Jim Mathies napisał:
> First off - allow me to say that this library has
> come a long way in a very short time! Very impressive.
> I'm thinking of using this in the application
> I'm working on. The freeglut lib would be contained
> within a dynamic lib.
</HUMBLE OFF>Cool.</HUMBLE ON>
> I'm curious about some things - these are based on
> the things in Glut's source I found to be intolerable.
> Here goes:
> - Is freeglut re-entrant? Are there any globals
> anywhere that would screw things up if multiple
> threads access the lib at the same time?
Context switching might be a bit sensitive to multithreading.
I believe that as long as you don't change the current window
(explicitly or by creating/deleting other windows) everything
should be OK.
> I notices the state stuff - this looks like it had
> this issue in mind...?
> - Does glutMainLoop return now? or how was the endless
> mainloop issue resolved?
glutMainLoop() returns when there are no more windows opened.
> - is there any printing to std fileio like stderr and
In freeglut? I don't think so. If there is, it can be removed.
> - does it use the call exit(0) anywhere? This really
> annoyed the heck out of me in glut. Nothing
> propagated errors back up to the main loop. resources
> where left unfreed. yuck!
> - Is there any sample source code anywhere? I couldn't
> find any. I'm curious how you init and shut down
> the lib properly.
Not many of those. I had some (*big* hehe) plans for freeglut,
its documentation and sample sources, but suddendly I run out
of time due to my studies :) Maybe I'll get back to freeglut this summer.
Sorry for the response delay, again, and thanks for the suggestions.
Pawel W. Olszta