Page 4 of 4

Re: "Must fixes" for next release

Posted: Tue Mar 04, 2014 4:59 pm
by gleepglop
http://newsgroup.xnview.com/viewtopic.php?f=36&t=20585 is destroying images by cropping the wrong part and not allowing it to be undone. This is in XnView version 2.13.

Re: "Must fixes" for next release

Posted: Mon May 05, 2014 9:49 pm
by gleepglop
gleepglop wrote:http://newsgroup.xnview.com/viewtopic.php?f=36&t=20585 is destroying images by cropping the wrong part and not allowing it to be undone. This is in XnView version 2.13.
Still permanently destroying images in XnView 2.22.

Re: "Must fixes" for next release

Posted: Sun Feb 01, 2015 10:34 am
by pia
Au premier scan d'un document avec le menu "acquérir dans" tout se passe bien.
Au scan d'un document suivant toujours avec le menu "acquérir dans", dès que je clique sur le bouton "scanneur", j'ai la fenêtre avec "xnview a cessé de fonctionner. Détails du problème:

Nom d’événement de problème: APPCRASH
Nom de l’application: xnview.exe
Version de l’application: 2.25.0.0
Horodatage de l’application: 5458e922
Nom du module par défaut: StackHash_0a9e
Version du module par défaut: 0.0.0.0
Horodateur du module par défaut: 00000000
Code de l’exception: c0000005
Décalage de l’exception: 00000000
Version du système: 6.1.7601.2.1.0.768.3
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 0a9e
Information supplémentaire n° 2: 0a9e372d3b4ad19135b953a78882e789
Information supplémentaire n° 3: 0a9e
Information supplémentaire n° 4: 0a9e372d3b4ad19135b953a78882e789

Merci de votre aide

Re: "Must fixes" for next release

Posted: Mon Aug 24, 2015 8:27 am
by BloodyRain
It'd be nice if this could finally be fixed http://newsgroup.xnview.com/viewtopic.php?f=36&t=31250

Re: "Must fixes" for next release

Posted: Sun Nov 01, 2015 5:14 am
by dev3d
Very often XnView gets into a corrupted state whereafter it will crash every single time on startup unless the startup window size and position lines are removed from XnView.ini, as reported in XnView Maximized Bug and Continually Crashes on Startup. It seems like this might be related in some way (regarding how window/screen position is used on startup) to another issue reported first in that thread regarding how maximized XnView moves to a different screen after relaunching it twice. This has been a longstanding issue and has resulted in XnView about 50 different instances where XnView becomes corrupted and never launches again.

Also, though unrelated, I would appreciate if you could fix it so that Alt-M shortcut for Move to folder... works again, as that was broken in the last release and I use it up to dozens of times a day when organizing media.

Re: "Must fixes" for next release

Posted: Sun Jan 01, 2017 10:04 pm
by helmut
Wrong mouse wheel behaviour in XnView 2.37 should be fixed real soon, see topic 2.37: Mousewheel navigation: Zooming instead of navigating for details.

Re: "Must fixes" for next release

Posted: Mon Jan 02, 2017 6:40 pm
by uRsti11anError
helmut wrote:Wrong mouse wheel behaviour in XnView 2.37 should be fixed real soon, see topic 2.37: Mousewheel navigation: Zooming instead of navigating for details.
According to announcement of version 2.39 and changelogs included, this issue was dealt with two versions ago. But since many other bugs were simply ignored, I don't see a reason to move further than 2.36.

Update: btw, you were the one celebrating it http://newsgroup.xnview.com/viewtopic.p ... 4r#p135427

Re: "Must fixes" for next release

Posted: Tue Jan 03, 2017 9:21 pm
by helmut
uRsti11anError wrote:
helmut wrote:Wrong mouse wheel behaviour in XnView 2.37 should be fixed real soon, see topic 2.37: Mousewheel navigation: Zooming instead of navigating for details.
According to announcement of version 2.39 and changelogs included, this issue was dealt with two versions ago. But since many other bugs were simply ignored, I don't see a reason to move further than 2.36.
Bugs that affect you might not have been fixed. For other people the minor enhancements and bug fixes might be of interest.
uRsti11anError wrote:Update: btw, you were the one celebrating it http://newsgroup.xnview.com/viewtopic.p ... 4r#p135427
Thanks for the hint, uRsti11anError. I mixed up versions and really forgot that the mouse wheel problem had been fixed in 2.38, already.

Re: "Must fixes" for next release

Posted: Sun Mar 19, 2017 8:59 pm
by dev3d
Could the following issues be fixed with the upcoming release?
  1. Sidecar/Companion Files and Move/Copy/Rename Dialog Issues
  2. XnView Maximized Bug and Continually Crashes on Startup (with updated/pinpointed Steps to Reproduce)
  3. Next/Previous Issues with Preview Pane

Re: "Must fixes" for next release

Posted: Sat Apr 01, 2017 10:29 am
by Paradroid
xnView 2.39, Monitor-Resolution 1920x1080

Some Dialogs are not usable in this resolution, because the Dialog-Window is too small and not resizable.

for example:
Shift+E (= Bild, Einstellen, Helligkeit)

In xnView MP those Dialog-WIndows are resizable.

Re: "Must fixes" for next release

Posted: Sun Apr 09, 2017 2:40 pm
by xnview
Paradroid wrote: Some Dialogs are not usable in this resolution, because the Dialog-Window is too small and not resizable.
for example:
Shift+E (= Bild, Einstellen, Helligkeit)
In xnView MP those Dialog-WIndows are resizable.
Please check here

Re: "Must fixes" for next release

Posted: Tue Mar 26, 2019 12:51 am
by Dwarden
are there any plans to update he archive modules ?
e.g. the UNACEV2.DLL distribued with Xnview has serious security flaw

please contact author of Total Commander, he patched the same version to prevent them

note: it would be wise to either deprecate all the obsolete addons
or do cleanup update for all to latest version e.g. unace, unrar, 7z etc.