CompuServe Messages

We found a bug in PPage, all versions. This is something that has been driving us crazy for years (literally!). The problem is this, PPage loses track of our bit mapped graphic images. We are using commercial clip art, which has several images on a page. We use the scale and crop features to zero in on a particular image on the page, and change its size to the size we need. What happens is when we print the document, we get the wrong graphic!. Ppage has chosen a different file for input, and applied the scaling and cropping intructions we set up. In other words, we get the right part of the page, scaled to the right size, but it's using the wrong d*mn page! Of course, this doesn't always happen, but it's almost guaranteed that sometime in the production of our newsletter it will happen at least once. I have spoken to Gold Disk a couple of times about this, but they haven't done anything. This problem goes back as far as release 1.3, 1.31, 2.0, and 2.0A. Having said all this, we have some good news. We always thought that the problem was occuring when we were saving the document, but it turns out that the problem occurs on the *load*, not the save. Because we have always had trouble with bit mapped graphics, we always load our bit mapped graphics when loading a document, so we can see if the images are loaded correctly. You can tell the images are going to be screwed up if it takes a long time to load the images. Accidently, we found that if the images are screwed up, then just re load the document, and chances are it will load correctly the second time. I mention this for 2 reasons, one: so anyone else who may be having this problem can use our solution, and two: now that we have a better idea of where the problem is occuring, perhaps Gold Disk can fix it (Are You Listening, GD?) Gene