Okay, I looked at the code for text3d again last night and I realized that it actually is okay...I just didn't document what I was doing very well. Not very efficient, but no memory problems. I will check for other bugs this weekend.
Later, Mark
============================ = mdanks@stormfront.com = http://www.danks.org/mark ============================
-----Original Message----- From: x7.382045·v [mailto:x7@jodl.org] Sent: Tuesday, March 14, 2000 5:52 AM To: Mark Danks Cc: pd-list@iem.mhsg.ac.at Subject: RE: gem
| Just looked at the code. Oh boy, bad memory leaks and other issues. I |can tell that no one has really hammered it. Look in TextBase::textMess() |and you will instantly see the problem.
yeah, not SO instantly .. but trying ..
.xo
| Okay, I looked at the code for text3d again last night and I realized that |it actually is okay...I just didn't document what I was doing very well. |Not very efficient, but no memory problems. I will check for other bugs |this weekend.
yup, let know .. textoutline seems more stable than text3d ...
but alos, the openGL accell in linux generally seems fairly wobbly_