Page 1 of 1

0.85b1: Contact sheet: Preview with special background color

Posted: Wed Mar 22, 2017 4:27 pm
by helmut
XnView: MP 0.85b1 - 64 bit
OS: Windows 7 - 64bit

When creating a contact sheet the preview uses a black backcolour. It's unclear where and how the user can set this background colour.

Effect: Irritating user interface.

To reproduce:
1. In XnView browser select multiple image files.
2. Select Create ยป Contact sheet
3. In dialog "Create contact sheet" check "Footer" and enter some text.
4. Switch to "Preview" tab.
Actual behaviour (bug): Preview tab is displayed. The preview is shown with a black background. :bug:

Expected behaviour: The preview should be shown with a standard background colour which can be set in XnView. E.g. the background colour of the "Preview" could be used.

Note:
The preview in "Print" dialog also has a different background colour.

Note: When checking "Header" and the preview is updated and contains both header and footer. Looks like setting footer doesn't trigger an update of the preview.

Re: 0.85b1: Contact sheet: Preview with special background c

Posted: Mon Mar 27, 2017 7:59 am
by xnview
it uses the default background color in sheet group (white)

Re: 0.85b1: Contact sheet: Preview with special background c

Posted: Mon Mar 27, 2017 12:19 pm
by xnview
ok, same bug as this one

Re: 0.85b1: Contact sheet: Preview with special background c

Posted: Mon Mar 27, 2017 2:26 pm
by helmut
xnview wrote:ok, same bug as this one
Pierre, on the technical level this might be the same bug on the user level these are two bugs. So let's keep these bug reports separate.

Just to make sure: I mean the surrounding background - not the background of the contact sheet:
Contact sheet-background.png

Re: 0.85b1: Contact sheet: Preview with special background c

Posted: Tue Mar 28, 2017 9:30 am
by xnview
This problem is supposed to be fixed in XnView MP 0.85 beta 3. Please check and confirm the bug fix here.

Re: 0.85b1: Contact sheet: Preview with special background c

Posted: Tue Mar 28, 2017 9:18 pm
by helmut
Confirmed fixed in beta 3. Thank you, Pierre!