XnView Software

Woow first time I checkout 1.90.. it's really great!

Do have one point (I am bit afraid to open a new topic, there are so many unique topics already!): When XnView is running and image A is opened in XnView, I might doubleclick image A in Explorer.. now Xnview doesn't go to the tab where image A is viewed, instead it opens the image in a new tab.

Same goes for Xnview browser, already opened images are opened again in a new tab instead of switching to the tab where the image was already opened.

As far I know all programs switch to the window with the existing file/document or ask if you want to return to the saved document.
I hope this will be fixed before the final release.

Also a little bug perhaps? I selected Favorites, added a whole partition (D). I tried expanding it and it was no problem. then I added My Documents. After that I tried to expand D again, nothing happens. Had to remove both D as well as My Documents and re-add them again.
But perhaps its not a bug and XnView was still busy indexing stuff from the large D partition.

<Moderator's notes:
- This topic has been split from another topic
- Please start a new topic for each suggestion/question - see Rules & Guidelines>

An option to open one view per image and reopening this view when opening this image, again, makes sense. A longer time ago, there has been discussions about the option "Open one view per image" which seemed to do what you (and other people want), but this option had a wrong name.

So your new request for such an option is good and makes much sense to me.

Related topics:
RC3: Option 'One view per picture" broken]RC3: Option 'One view per picture" broken
'Open one view per selected image' unneeded?
rc2: multiple view options conflict.
One tab per image when double-clicking

ZileXa wrote:Also a little bug perhaps? I selected Favorites, added a whole partition (D). I tried expanding it ...

Could you please post this bug report in a separate topic in forum group "1.90 Testing - New/Open"? Please mention the exact version (e.g. 1.90 RC1), then.

I've been complaining about this behaviour for a long time now. Good to see that other users think alike. Show your support, people!

Danny wrote:I've been complaining about this behaviour for a long time now. Good to see that other users think alike. Show your support, people!

I support this.

This behaviour is not so confusing anymore since there are tabs and the user sees what is going on. But I also think that the tab already opened should be simply brought to top (raised) instead of opening another tab.

Some people might like the current behaviour, so an option for this might be good. The option should default to the new behaviour (i.e. raise tab if already opened).

helmut wrote:

Danny wrote:I've been complaining about this behaviour for a long time now. Good to see that other users think alike. Show your support, people!

I support this.

Me too.

Maybe what's needed is a sort of intelligent reopen - if the image has been edited and unsaved, then it'll open a new tab, whereas normally it'd just take you back to the old tab. After all, editing is the place where you might want several copies open, and it makes for a reasonably convenient method. (Although a "clone to new" option might be just as convenient and more consistent.)

foxyshadis wrote:Maybe what's needed is a sort of intelligent reopen - if the image has been edited and unsaved, then it'll open a new tab, whereas normally it'd just take you back to the old tab. After all, editing is the place where you might want several copies open, and it makes for a reasonably convenient method. (Although a "clone to new" option might be just as convenient and more consistent.)

Interesting idea. I love and support it!

Congratulations Pierre, with this milestone release!

That said, I cannot understand why "One Tab per Image" STILL has not been implemented.. there have been many topics, since v1.80 I believe..
Now we are months if not year later and still... I didn't had time to read all the feedback untill today. I really expected this feature to be on the list to implement for 1.90.
It's a bummer cos I like the update, but on the other hand this big issue hasn't got any attention.. again.
I hope Pierre can give some info about if it will ever be implemented.

I'm sorry if this is a bit disrespectful.. that is not my intention.