CompuServe Messages

I fingered it out just a little while ago. 🙂 🙂 Its one of those where you wanna hit yourself, but never considered masicism very fun. I had read a few days ago that you must have an even number of bytes in the bitmap.rowBytes field. So I took care to declare my bitmaps so that rows ended on word boundaries. But I have some other code that crops a bitmap after I'm done putting together what amounts to a collection of smaller bitmaps (font chars, tiff images, etc., this is very portable code). To make a long story short, the cropping routine didn't try to word align the rows, so I would get these weird crashes on 68000 based machines where sometimes it worked and sometimes it didn't. What surprised me was that it would work fine on 68030 machines regardless of the row aligned, but not on any 68000 machines, viz., SEs and old Classics. Anyhow it feels great to move on. And it was a real pain to have to hunt down an SE or Classic every time I thought I found something that MIGHT fix it. Thanks for the input. "I dread the day when they will have a choice, then we'll have to coax 'em into doing what we want." Jody