XnView Software

Some cameras does this: Showing saturated areas in the image so you know that you should select a different setup and take another picture.
The pixels where the numeric values reaches 253-255 are blinking in shades of greys, indicating near-saturation. Why not having this feature embedded in XnView MP?

That's a common issue when adjusting color/contrast / Brightness / Gamma... to reach the limit of the dynamic range in one or more color plan, destroying the actual colours. Shift-Ctrl-I allows to chase in zones that we suspect are close to the limits. The histogram helps but is not as obvious as the blinking pixels. This could be activated / deactivated as a general option (excluding fullscreen) or specifically in dialogs that allows these changes.

The same could be done for dark areas (any colour very close to 0).

Related topics:

• More custom option during RAW convertion
• Highlite Overexposed Areas
• Feature Suggestion: Shaddow/Highlight
• Status bar-settings

I didn't found these requests on overexposed / underexposed areas. Thank you.

In the mean time, can we have the Histogram feature enhanced a bit to allow Ctrl-Z?

In the current version of XnViewMP, it's a static graph linked to the existing file content so when doing adjustments the graph doesn't change.
To evaluate the result we need to save the file and close/reopen (or navigate to next picture / go back.

This kills any possibility to do fall-back via Ctrl-Z

Thank you

B.Douille wrote:I didn't found these requests on overexposed / underexposed areas. Thank you.

In the mean time, can we have the Histogram feature enhanced a bit to allow Ctrl-Z?

In the current version of XnViewMP, it's a static graph linked to the existing file content so when doing adjustments the graph doesn't change.
To evaluate the result we need to save the file and close/reopen (or navigate to next picture / go back.

This kills any possibility to do fall-back via Ctrl-Z

Thank you

This is very important and will get overlooked here. You need to start a new thread with this. But the problem isn't Ctrl-Z. It that the Histogram is useless/wrong because is desynced from the actual picture at first edit. When the screen image is updated the histogram (if visible) needs to be also updated.