Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thumbnail View render time #100

Open
kefir- opened this issue Nov 16, 2012 · 3 comments
Open

Thumbnail View render time #100

kefir- opened this issue Nov 16, 2012 · 3 comments
Labels

Comments

@kefir-
Copy link
Contributor

kefir- commented Nov 16, 2012

Testing on a fairly typical Windows image in a E01 image, the Views -> File Types -> Images had 46 pages of images, with 200 images per page. It often took up to a minute to render the 200 thumbnails of the images on a single page, so browsing through can take a long time. (Ingest is running in the background, but only consuming around 12% CPU, and the network is not congested).

When I start browsing the images, it would be useful if Autopsy pre-renders pages in the background to save the operator time later.

Alternatively, it would be nice if Autopsy rendered all the thumbnails into a single page, and only rendered "on-demand" whatever is in the view at the time (plus a little extra for scrolling?). That would make it easier to browse through all the entries, and jump to a given offset. Currently, there is no way to jump to a given page of thumbnails, it seems I have to click 45 times to get to page 45 of thumbnails, or 25 times to get to page 25 even if page numbers loop. This change would solve that as well.

Finally, it would be useful if the GUI remembered which entry is selected when switching between Table View and Thumbnail View, so that it displays the same entry and offset when changing views.

@ghost ghost assigned adam-m Nov 26, 2012
@adam-m
Copy link
Contributor

adam-m commented Jan 18, 2013

Can now jump to any offset.

@kefir-
Copy link
Contributor Author

kefir- commented Feb 27, 2013

That helps! But scrolling sideways between bunches of 200, and then up and down to see those 200 images isn't ideal. I think it would be better to either:

  1. Scroll sideways from page to page, fitting the number of images to the available area, or
  2. Scroll up and down to see all images.

Loading of images still takes a while, and I've noticed that small images are scaled up to fit into the space for each image. Probably a minor optimization, but small images could probably remain small here.

@adam-m
Copy link
Contributor

adam-m commented Mar 6, 2013

Finally, it would be useful if the GUI remembered which entry is selected when switching between Table View and >Thumbnail View, so that it displays the same entry and offset when changing views.
I believe the selections are being preserved, could you let me know if not the case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants