[KPhotoAlbum] Zooming issue

[Johannes Zarl-Zierl]

Hello Angel,

Sorry for not getting back to you sooner!

I have some further questions for you:
You've written that you saw the problem for some time now. Do you know when it 
started initially?

I assume that fullscreen vs. windowed viewer does not make a difference…

Do you have the same problem with all images, or is it dependent on the image 
size? Do you see the same problem with the demo image set?

Cheers,
  Johannes


Am Mittwoch, 17. Oktober 2018, 00:52:38 CEST schrieb Angel Lopez:
> I did the suggested modification but it makes no effect. Indeed, the
> function "zoomPixelForPixel", had it already reversed. So commenting
> "potentialyLoadFullSize" in the zoom() function, solves the problem for
> mouse zoom and "+" and "-" keyboard zooming, but pressing "=" for zoom
> pixel for pixel, still goes wrong (as potentialyLoadFullSize was not
> commented inside it).
> 
> So, with a call to potentialyLoadFullSize commented inside zoom, behavior
> is as expected and very fast zooming.
> With that call not commented, but "m_reloadImageInProgress = false" inside
> the function "potentialyLoadFullSize" (original value was true) Then after
> zooming it goes back to original. But it takes some time (like one second
> in my computer)
> 
> 
> As additional information, I'm working on an old laptop with screen
> resolution 1366x768.
> 
> If you want I can do all the test you want.
> 
> Thank you again !!
> 
> Regards,
> 
> Angel.
> ______________________________
> ----------- Angel ------------
> 
> 
> 
> El mar., 16 oct. 2018 a las 22:42, Johannes Zarl-Zierl (<
> 
> johannes at zarl-zierl.at>) escribió:
> > Hi Angel,
> > 
> > Am Montag, 15. Oktober 2018, 00:42:26 CEST schrieb Angel Lopez:
> > > In ImageDisplay.cpp:
> > > in function: void Viewer::ImageDisplay::zoom( QPoint p1, QPoint p2 )
> > > 
> > > if I comment out : potentialyLoadFullSize(), then it works as expected
> > 
> > (not
> > 
> > > exactly because the first time I draw a rectangle no zoom if performed).
> > > It seems that a call to potentialyLoadFullSize() is already made in the
> > > resizeEvent()  function.
> > 
> > That is kind of surprising, because the potentiallyLoadFullsize() does not
> > (directly) manipulate the view position or zoom level. I'm suspecting that
> > it
> > interacts with cropAndScale() and causes that function to misbehave…
> > 
> > Can you try and see what happens if you switch the position of the
> > potentialyLoadFullSize() call with the call to cropAndScale(), i.e. what
> > happens if cropAndScale is done *before* potentiallyLoadFullSize?
> > 
> > 
> > Cheers,
> > 
> >   Johannes