I'm running into some odd behaviour with BSetroot/BSetbg.
When setting an image via console, e.g.
bsetbg.exe -full pathtoimage.jpg
I get image artifacts.
See the first attachment.
If I set the same image via drag&drop, it displays just fine.
See the second attachment.
I first thought this was due to stretching the image but it happens even with images at my native monitor resolution.
It is obvious that drag&drop and command line input are handled differently by Bsetbg and I'd like to know why.
The readme for Bsetbg* says that it can use another application for displaying wallpapers via the "-app" parameter, so I suppose that drag&drop makes bsetbg look for the default image viewer app and then uses it to display the image.
I've tried the "-app" option in a command line with a path, without a path, with the path in quotes, without the path in quotes...to no avail.
Does anyone have an idea what's going on here?
Any way to log BBZero?
*https://github.com/a...r/README.bsetbg