My dad has some random HP Photosmart scanner and keeps running into problems with it and ReceiptWallet. His messages imply that it is an issue with ReceiptWallet and that very well may be the case. I looked at his ReceiptWallet log today and saw:
XResolution: 200.0000 YResolution: 200.0000 imageInfo: ImageWidth: 616 ImageLength: 1528 SamplesPerPixel: 3 BitsPerSample: 5605 BitsPerPixel: 16815 Planar: 0 PixelType: 2 Compression: 0 got the image info 0... setupMemXfer.MaxBufSize: 16777216 setupMemXfer.Preferred: 1048576 bytesPerRow: 0 Getting image via memory based transfer... totalMaxDestBytes : 0 rc: 1 Got image via memory based transfer: 1
This means that the scanner says that it has 16815 bits per pixel! Most scanners do 24 bits per pixel. His scanner must be so advanced that it can capture color 800 times better than the average scanner! OK, so the scanner reported an error and somehow ReceiptWallet didn’t properly handle this (I think I fixed this). The better question is why oh why do HP scanners report bogus information? It seems like the HP scanners are the ones that randomly screw up scans the most. I worked on an issue last week with a different HP scanner doing something similar. Did I mention that the scanner logs debug message to the Console? This is very bad form in a shipping app. ReceiptWallet’s debugging information is turned on via a hidden switch and logs it to its own file to make it easier to troubleshoot. I’m hoping that someday the drivers get better.