🚀 go-pugleaf

In article <3502@rosie.NeXT.COM> aozer@next.com (Ali Ozer) writes:
> done that, the problem goes away. Your bug sounds like that problem, and if
> they're the same, then, yes, it's a NXImage bug, and it's fixed in 3.0. 

Yeah, right.  Will they fix the lockFocus as well, or maybe the Bitmap  
rendering, or maybe the screen rendering, or maybe the fact that the NXImage  
object is too slow to render most images.

I had to re-write the NXImage object because NeXT didn't do it right the first  
time, the damn thing is too slow rendering and god forbid you actually want to  
make a bitmap of anything at any size.  It's great if you want to render an  
image that is only, say, 512k x 360k.  Now, let me ask you this, have you tried  
rendering, let alone locking focus on, a 2k x 2k image that has 700 dpi worth  
of data?  Takes a bit of time eh?

I hope NeXT has changed the NXImage class drastically, otherwise we, as a  
platform, are doomed for any type of high-end imaging.

Also, something else to think about, I've seen a person who was working on an  
image rendering project on a color station with 16MB RAM, and I've seen the  
computer crash because the damn thing rendered so many reps, it wasn't funny.

I seriously hope that these problems have been fixed, re-writing the NXImage  
object wasn't fun...

J. Alexander Jamison, disgruntled programmer
Sr. Systems Engineer
Talus Imaging and Communications Corp.