Page 1 of 2
0.68 viewer zooms in every image
Posted: Mon Jul 21, 2014 4:59 pm
by stravamir
So every time I open an image the viewer zooms in stretching the image across the screen. This is pointless, can I turn this off? I would like images to be displayed in 1:1 zoom by default.
Thank you.
Re: 0.68 viewer zooms in every image
Posted: Tue Jul 22, 2014 7:37 am
by xnview
do you have changed the 'auto image size'?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 11:01 am
by stravamir
Where is auto image size?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 12:53 pm
by cday
stravamir wrote:Where is auto image size?
When you have an image displayed In the Viewer: View > Auto image size
(If none of the options available address your problem, please describe it in more detail.)
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 12:57 pm
by stravamir
It is set to "no fit". But the image is always fitted.
The solution is to set it to "Fit image to window, large only".
Thank you for helping me.
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 1:21 pm
by cday
stravamir wrote:Thank you for helping me.
I have thought before that 'Auto image size' is not very clear, but it has been used in XnView Classic for a long time...
View > Fit image to... seems clearer to me, although I'm not sure if the ellipsis (...) conforms to normal conventions.
Any other comments or suggestions?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 1:36 pm
by stravamir
It's just a bit unexpected for a content of a view menu to change when a user switches from browse to view tab.
I was expecting those options in settings. But it was a limit on my view on a problem.

So, it's cool I guess.
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 2:02 pm
by cday
stravamir wrote:It's just a bit unexpected for a content of a view menu to change when a user switches from browse to view tab.
Yes, and not just the View menu...
It can confuse new users at first, but XnView has a highly developed browser that is the major attraction for many users.
cday wrote:I have thought before that 'Auto image size' is not very clear, but it has been used in XnView Classic for a long time...
View > Fit image to... seems clearer to me, although I'm not sure if the ellipsis (...) conforms to normal conventions.
Anyone else care to comment or have a suggestion?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 5:23 pm
by m.Th.
cday wrote:stravamir wrote:Thank you for helping me.
I have thought before that 'Auto image size' is not very clear, but it has been used in XnView Classic for a long time...
View > Fit image to... seems clearer to me, although I'm not sure if the ellipsis (...) conforms to normal conventions.
Any other comments or suggestions?
ellipsis (...)
in GUI conventions means either a dialog either a submenu.
It's just a bit unexpected for a content of a view menu to change when a user switches from browse to view tab.
I was expecting those options in settings. But it was a limit on my view on a problem.

So, it's cool I guess.
Hm, yes and no. Because the main purpose of XnView is to be browser/viewer/organizer this means that such things are sometimes rather often used, hence they must be surfaced closer to user (menu, shortcuts etc.) and not buried deep down in settings.
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 7:30 pm
by cday
m.Th. wrote:ellipsis (...) in GUI conventions means either a dialog either a submenu.
Thanks, I've Googled a bit and need further thought for a full understanding, but in this case the arrow to the right of the View menu item means an ellipsis is certainly not needed.
cday wrote:
I have thought before that 'Auto image size' is not very clear, but it has been used in XnView Classic for a long time...
View > Fit image to... seems clearer to me, although I'm not sure if the ellipsis (...) conforms to normal conventions.
Any thoughts on whether
View > Fit image to (with arrow) is clearer than 'Auto image size' and might assist new users?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 8:15 pm
by XnTriq
MarkJ (Stack Overflow » [url=http://www.stackoverflow.com/questions/637683/when-to-use-ellipsis-after-menu-items#637708]When to use ellipsis after menu items[/url]) wrote:Microsoft Windows applications are
supposed to follow
Microsoft's "User Experience Guidelines". Here's what they say about ellipses on menu items.
While menu commands are used for immediate actions, more information might be needed to perform the action. Indicate a command that needs additional information (including a confirmation) by adding an ellipsis at the end of the label.
This doesn't mean you should use an ellipsis whenever an action displays another window—only when additional information is required to perform the action. For example, the commands About, Advanced, Help, Options, Properties, and Settings must display another window when clicked, but don't require additional information from the user. Therefore they don't need ellipses.
David's answer cites the
KDE 3 user interface guidelines,
Notice that every item in a menu that first opens a dialog requiring additional information must be labelled with a trailing ellipsis (...) (e.g. Save As..., Open...). There's no space between the menu item and the "...". A simple confirmation dialog is not considered a dialog that requires additional information.
The
Apple Human Interface Guidelines say:
When it appears in the name of a button or a menu item, an ellipsis character (…) indicates to the user that additional information is required before the associated operation can be performed. Specifically, it prepares the user to expect the appearance of a window or dialog in which to make selections or enter information before the command executes. Because users expect instant action from buttons and menu items (as described in “Buttons” and “Menu Behavior”), it's especially important to prepare them for this alternate behavior by appropriately displaying the ellipsis character. The following guidelines and examples will help you decide when to use an ellipsis in menu item and button names.
Updated URLs (quoted text subject to linkrot):
- KDE TechBase: Human Interface Guidelines
- Mac Developer Library: OS X Human Interface Guidelines
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 9:00 pm
by cday
It's confusing, at least without very careful reading and reconciling of the various references: in 'View > Auto image size' a 'window' (of sorts) opens when the item is clicked, and it is (for sure) necessary to make a selection before any action occurs...
In practice, the arrow at the right end of the menu item clearly overrides any possible need for an ellipsis, so my question was actually unnecessary!
Here's another link that discusses the use of 'ellipsis' and 'arrow' affordances [sic]:
http://uxmovement.com/buttons/how-to-us ... fordances/
Meanwhile, I've started a debate but not the one I intended...
cday wrote:
I have thought before that 'Auto image size' is not very clear, but it has been used in XnView Classic for a long time...
View > Fit image to... seems clearer to me...
Any thoughts on whether View > Fit image to (with the arrow) is clearer than 'Auto image size' and more intuitive for new users?
Re: 0.68 viewer zooms in every image
Posted: Wed Jul 23, 2014 9:30 pm
by XnTriq
cday wrote:Any thoughts on whether View > Fit image to (with the arrow) is clearer than 'Auto image size' and more intuitive for new users?
I'm in favo(u)r of your suggestion.
- Fit image to »
- No fit
————————————
Window
Window, large only
Window, small only
Window width
Window height
Window width or height
Re: 0.68 viewer zooms in every image
Posted: Fri Jul 25, 2014 8:09 am
by xnview
XnTriq wrote:
- Fit image to »
- No fit
————————————
Window
Window, large only
Window, small only
Window width
Window height
Window width or height
everyone is agree with this change?

Re: 0.68 viewer zooms in every image
Posted: Sat Jul 26, 2014 7:25 am
by m.Th.
Generally I agree with the idea but the thing was discussed before:
http://newsgroup.xnview.com/viewtopic.p ... 19#p112515
And I think that perhaps in the thread above is a more flexible approach.