"Never ask again" option after changes

[Silesian]

In many cases I need to temporarily correct the brightness, for example, to be able to read old books better.
In Xnview Classic there is a very useful option so that within a session this question is no longer asked.

2023-03-24_092416.png

I would like to have this option also in XnView MP.

[xnview]

do you have checked this topic

[Silesian]

Yes I did, but savingChanges=1 or savingChanges=0 (static setting) does not have the function as realized in Xnview Classic (dynamic overwrite), as described above. I tried both settings, but I cannot prevent the same question from being asked again and again within a session.
Or am I not understanding this correctly?

[xnview]

you would like to always save?

[Silesian]

A static "Always save" or "Never save" is no option in my usecase.
Often I need a temporarily correction of brightness or ... to better read old writings.
Xnview Classic delivers the right "Never ask again" option, which is valid within a viewer session of consecutive images.

It would be very useful to have this option also / again in Xnview MP.

[xnview]

See issue for current status and some details.

[xnview]

This problem is supposed to be fixed in XnView MP 1.4.5. Please check and confirm the bug fix here.

[Silesian]

Thanks, in princip it is working correct in 1.4.5. The differences to Xnview Classic are:

- the default button is "Save" and not "Cancel", this is more risky with accidental use of ENTER
- the question posed above: "Do you want to save..." is confirmed with "Yes" or "No" in Classic. This is more logical for me.

2023-05-10_163929.png

[xnview]

- the default button is "Save" and not "Cancel", this is more risky with accidental use of ENTER

ok

- the question posed above: "Do you want to save..." is confirmed with "Yes" or "No" in Classic. This is more logical for me.

but we have 'save as'

[Silesian]

- the question posed above: "Do you want to save..." is confirmed with "Yes" or "No" in Classic. This is more logical for me.

but we have 'save as'

Ok. but you added a 2nd additional save option compared with Xnview Classic.
Perhaps you could visually redesign the dialogue to better separate the two variants.

What's about this or a similiar solution?

2023-05-10_195234.png

"Save as" could also move to the right side (with more space for long filenames).
Longer filenames should be possible or shortened.

[xnview]

yes better, See issue for current status and some details.

[user0]

actually I'm looking at dialog boxes right now for a separate post, but since you touched this one already )

first of all I would check how it is done in some other apps, than I would check some UI guidelines for desktop apps, eg
MS design guidelines for:

• Confirmations advises to use Save and Don't save buttons as it provides obvious reason for the confirmation

• Dialog Boxes advises similar about Cancel button, but we are good here

so I'd rather change it as following:
- do not move default focus from Save, as this is pretty much standard behaviour
- remove titlebar icon
- change phrase to "Don't ask again" and use the same one across app
- (optional) move file name to the 2nd line, not per guidelines,
but I find it easier to get information this way and it allows to avoid breaking long names to the second line

msg_save_as.png

[xnview]

Photoshop use Yes/No/Cancel

[user0]

Photoshop use Yes/No/Cancel

yep, they have not followed system design guide, same as others
but imho Save/Don't save visually reads better

other_apps_save.png

[Silesian]

Compared to Xnview Classic an additional Save option has been added in "MP" (Save As), see:
viewtopic.php?p=186148&sid=7c398e40a277 ... 49#p186148.

Both options should not be stuck together optically. The question "Save Changed File" can be answered "Classic" (Yes/No) or additionally with "Save As". There must be an optical space between them, see
viewtopic.php?p=187630&sid=7c398e40a277 ... 49#p187630.

The filename should be separate in the line and there should be enough space for it.

The familiar behaviour and clarity is more important to me than UI guides. Let Pierre do it.