The v12beta version seems to miss the "keep zoomed position while flipping images" feature or is it me using the viewer incorrectly?
Thanks! o)
Edit: Smiliar thread, same topic:
resource.dopus.com/viewtopic.php?f=3&t=27172
I've been wondering about that myself. It definitely no longer keeps the scroll position when changing images; I haven't yet checked if it still did in 11.18, and if it was an intentional change (whenever it happened), but I think you are right that it changed at some point (or we've both changed a config setting somewhere and not realised the effect).
I used to dislike that feature, or thought I did, but having used the new viewer a bit I think maybe it was better having it than not. It's not always what I want to happen, but it turns out resetting to (0,0) isn't always what I want either. Don't know if other people feel the same.
For example, if i read comic files (like cbr/cbz), it would make a lot of sense, to keep the zoom ratio when flipping pages. In that case, i'd prefer the viewer to start in the 0,0 position, since that is, where the new page / panel starts.
So yes, keep zoom factor or not and keep scroll position or not have their use cases I think. Jpegviewer has a hotkey to (un)lock zoom/scroll position, maybe that's the way to go here as well. I regularly zoom in and flip images back and forth to compare some images close up, something I'd definitely miss in the long term.
I just came to say this too. Dopus 12 broke image viewer position in zoom view.
This was something I used everyday with Dopus 11. To compare two images details. I zoomed in and flipped through the images. Now if you go to the next image, the place of zoom is lost and reset to 0.0. Please fix this back which worked perfectly in Dopus 11.
Any updates on this? It's very annoying.
It was changed back some time ago. Is your install up to date?
When did it break and when was it fixed? I noticed it started on V11. Was it ever fixed for that?
I bought a second licence for 12, I'll try it.
AFAIK it was never an issue in Opus 11.
Recent versions of Opus 12 should behave the same as Opus 11, 10, etc. used to.
If you're seeing differently, please describe exactly what you're seeing and which version you see it in.
On 11.19 x64, if I scroll an image, then move the next image in sequence, the scroll position is always reset to the top left corner.
Previously it would remember where I had scrolled to and apply the same positioning to the next image.
Is this not the same issue?
Sounds the same, yes.
I'm surprised if it affected Opus 11, but maybe it did with 11.18 or 11.19.
As far as I know, all reports about it were from people noticing it when moving to Opus 12 (betas), so it was assumed to be something that changed during Opus 12 development. Either way, it has been changed back to the old behavior in recent versions, so Opus 12.3 should have the same behavior as, say, Opus 11.1.
I'll check the change logs, see if I can downgrade. I'm hesitant to upgrade because of stuff like this... I just want stability and know all the issues with 11 that affect me.
What is your policy on charges like this? I'd be very interested in a stable version that only gets critical and bug fixes.
Opus 11.19 was the last Opus 11 update. After several years of them we have to stop at some point to focus on Opus 12.
This would not qualify as a critical bug fix even if we were doing more Opus 11 updates.
Opus 12 is stable. If you want the latest tweaks, fixes and features, staying on an old version forever isn't the way to go.
Sure. What I mean is that at some point you updated 11 and broke it. If you had a stable branch that only got critical fixes rather than new features and on-going improvements that probably wouldn't have affected it.
I haven't bothered with 12 yet as there is no compelling reason to. If I update now it will be annoying because the only reason is to fix something you broke and didn't fix before moving on, and there are bound to be other issues with 12 anyway. Rolling back seems like a better option if we can find where it broke.
I'm guessing it's before the Heartbleed fix. I seem to recall that only affected FTP, right?
If you go back to 11.17 the old behavior is there. I did a check and 11.18 introduced the change, which is also in 11.19.
What you're asking for would be a HUGE burden to maintain, as it's very difficult to port fixes to divergent code branches (you are often really writing the same fix twice; fixes often depend on other changes which may not exist on the other branch). It'd be likely to increase bugs, not decrease them, as well as complicating support as people would be on various different branches.
There's a 24 minute video of just the highlights of Opus 12 but if you really don't think it's worth it, despite already owning it (if I understand correctly), then stay on 11.17 forever; your choice.
Heartbleed was a long time ago, around Opus 11.1 or 11.2 I think. Not relevant here.
Okay, thanks. I have the basic edition or whatever it's called of 12, from the Humble Bundle sale, but my main system uses 11 which I have a full licence for.
Having watched the video, maybe it is time to think about upgrading. High DPI support and loading the next image while viewing the current one would be nice. I have found some other issues with the image viewer but didn't bother report them because 11 is no longer supported. Actually I think I reported the scaling quality issue back with V9 but it's still there at least as of 11.