Hello Jan-Erik!
The visual artefacts appear here as well. it's part of DrDialog but resolv if you adjusst the window size >>>>slightly<<<< so that it can recalculate the position of controls and reposition/redraw them.
Yup, and honestly these are tiny things, so easy to deal with.
I'm adding code to set the(same) resource id after it has resized to allow it to redraw and hope that it will improve things for most cases.
OK good stuff, this is working well.
So can I 'push my luck" some more??? LOL
How about the other additional feature request:
1) could we add the file format choice?
I prefer to save my old Auto Parts Books scans in TIFF and optionally do some post processing on these in PMView, etc.
I'm looking in to that.
BUG REPORT
=========
1) CROP function, in my case the crop is incorrect, meaning the wrong part of the image is cropped. Take a look please at the attachments.
Have you seen the little button that should resemble a ruler (1...2] to the left?
Click on it and entry fields appear (though sometimes not fully visible).
That's the numbers (in mm) that it send to sane, and visible in the title bar during scan.
I suspect that sane ignore them, or that this backend perhaps require other parameters?
PMInSANE currently query the found scanner for information as it launch.
'@scanimage -h -d' device '|RXQUEUE'
and determine vertical range with
PARSE VALUE tmp WITH '-t'nt'..'xt'mm'
can you send me the output of:
'@scanimage -h +-d' device '>scan.log'
2) DEVICE select doesn't work: using "-DEVICE hp:libusb:003:001" in the program object parameter field results in that initial pop-up progress window just being blank, and any scanner commands afterwards do not produce any results
Yes, as you override the procedure to query the scanner, it doesn't show "progress", just pop up the main window when ready.
It just pass the parameter on to scanimage.exe and here it (scanimage.exe) hummmm and cause the scanner to scan, but I only have this one.
But scanimage doesn't even start as you add the parameter? I've only seen that scanimage refuse to do anything (just stall) in combination with chkdisk and had to restart the computer and use scanimage before chkdisk.
EDIT => nope, turns out that passing ANY parameters causes the outcome I wrote above, it is not just the '-DEVICE' one which I initially thought...passing '-O Y:\tmp' (which is my RAMDISK) produces the same result.
Strange, restart the computer and try again

Here it scanimage send the output to -O C:\var\temp\
Note the trailing \ try that as well
Is it possible to write tmp.pnm on Y: as the parameter you've set suggest?
and Y:\tmp.pnm isn't blocked?