Thought I should mention this. I have noticed a pattern: perhaps only because of the Freeglut/win32 problem in which it pegs the cpu at 100% forcing heroic measures to stop it, often after landing in a backtrace and fixing a bug and running again I end up with an access violation on a simple call into the FTGL. Then I have to exit Lisp and come back in. Not good, obviously, and something to be addressed before not too much longer, but for now if you suddenly see something like that you might want to try bouncing the Lisp.
kenny
Hmmm, not sure this always works, but just now I remembered to try the AllegroCL/win32 unload-library function on the ftgl DLL and I was able then to run without a problem. Check out a function called XFTGL for deets.
Just for fun over here I have added sliders to control all the parameters of the functions such as glut-wire-sphere (that one has size, stacks and slices) and I am just having a ball over here watching what happens as parameters are moved to their lower extremes. screen shots no longer suffice, because a lot of the fun is in dynamically working the sliders. Animated GIF? Hell, I can use command-line ImageMagick. Hmm...
:)
kenny
Kenny Tilton wrote:
Thought I should mention this. I have noticed a pattern: perhaps only because of the Freeglut/win32 problem in which it pegs the cpu at 100% forcing heroic measures to stop it, often after landing in a backtrace and fixing a bug and running again I end up with an access violation on a simple call into the FTGL. Then I have to exit Lisp and come back in. Not good, obviously, and something to be addressed before not too much longer, but for now if you suddenly see something like that you might want to try bouncing the Lisp.
kenny
-
Kenny Tilton