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

Supporting preserveViewport in OSD #1332

Closed
tangfucius opened this issue Mar 12, 2017 · 3 comments
Closed

Supporting preserveViewport in OSD #1332

tangfucius opened this issue Mar 12, 2017 · 3 comments
Labels
Mirador 2 Mirador 2

Comments

@tangfucius
Copy link

Although the 'preserveViewport' property is set to true when Mirador initializes the Openseadragon viewer, the viewport position/zoom level always resets to default when clicking through the images. Can this feature be easily activated in Mirador? If not, can someone give me an outline of how I can implement it myself?

@radpet
Copy link
Contributor

radpet commented Mar 12, 2017

Hi,

The osd resets the bounds because a new instance is created on each new image, thus making the value of this property more or less useless. A workaround would be to save somewhere the last bounds, attach to the osd open event and change the new image bounds

@tangfucius
Copy link
Author

Thanks @radpet ! Imageview provides a setBounds function, so I just need to call it within updateImage. The client side works pretty much as expected now, but now I see a couple of new problems:

  1. Does Mirador come with something like a spinner when an image is loading? My images are pretty big and can take a while to load.
  2. OSD keeps throwing Image timeout exceeded errors, probably because my IIIF image server can't handle that many requests at the same time. Is it possible to have Mirador to try reloading the image if it fails?

Sorry for these being unrelated to the topic. Just thought it might be more convenient to ask them in the same thread.

@camillevilla
Copy link
Member

This ticket is being closed as part of the Mirador 3 issues review. We encourage all Mirador 2 implementers to try out Mirador 3 and leave feedback in new tickets.

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

No branches or pull requests

4 participants