Project

General

Profile

Feature #8476

Panning images shouldn't need rough preview

Added by internetbummer - about 7 years ago. Updated about 6 years ago.

Status:
Triaged
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
Due date:
% Done:

20%

Affected Version:
System:
bitness:
64-bit
hardware architecture:
amd64/x86

Description

When translating the image, why do we use the back-buffered preview as opposed to just loading a larger section of the image behind the scenes and translating that? Once it's been translated too far, we can load additional sections of image. At the very least, we should just be able to pan the part that's on the screen and have rough previews only for the sections that aren't loaded yet. Why throw away the nicely rendered parts we already have?

On a lesser scale this is also a problem for zooming images. Instead of using the extremely rough preview, can't the existing view be used and interpolated before the newly zoomed image is loaded? This is especially true of zooming in, where the viewport already contains an image much closer to the next desired view than the strongly pixelated preview.

These are the visual details that, if done properly, will allow people to forget that they're using a program at all and really let them focus on what they're doing.

I'm digging around in the code trying to figure out how all the pieces fit together before I attempt to look at this. If you can point me to a few key areas I can see what sort of improvements I can bring about in these areas.

History

#1 Updated by Simon Spannagel about 6 years ago

hm, maybe would be a nice feature to have processed some area around current roi.
Set to future.

#2 Updated by Tobias Ellinghaus over 5 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Triaged

Also available in: Atom PDF