These are chat archives for openseadragon/openseadragon

7th
Jul 2015
Antoine Vandecreme
@avandecreme
Jul 07 2015 12:32
What version are you using? I did some change on onTileLoad recently so it would be nice to see if you reproduce both on master and 2.0.
IIRC, goHome is just panning and zooming
Grant Echols
@gechols
Jul 07 2015 14:41
I'm using 2.0.0 - I'll give master a try.
Grant Echols
@gechols
Jul 07 2015 15:11
@iangilman - can you look at openseadragon/openseadragon#680 - it adds a column configuration we need to the image collection feature.
Grant Echols
@gechols
Jul 07 2015 15:28
@avandecreme - the tile loading problems happens on master as well.
Antoine Vandecreme
@avandecreme
Jul 07 2015 15:31
thanks for testing, we will need to investigate then
Grant Echols
@gechols
Jul 07 2015 15:53
@avandecreme would it help to have a functional app to demonstrate the problem? I could have one published later today if it helps
Antoine Vandecreme
@avandecreme
Jul 07 2015 15:54
Most def, I am not sure I will have time to look into it for now though.
Ian Gilman
@iangilman
Jul 07 2015 16:22
@gechols Regarding your tile load issue, try setting the imageLoaderLimit in your options. Maybe start with 4 and work your way back up. By default it's on "unlimited" which may be causing it to try to do too much.
@gechols I'll take a look at #680; thanks!
@gechols And yes, doing some detection on the pan event is your best bet for knowing when you've gotten off of the images you've already added. You might also want to watch the zoom event, because zooming can reveal empty canvas as well
VoidVolker
@VoidVolker
Jul 07 2015 16:34
@iangilman hi! how I can help to fix openseadragon/openseadragon#555 ?
Ian Gilman
@iangilman
Jul 07 2015 16:38
@VoidVolker Seems like some error is accumulating for each time we wrap around, and it's especially noticeable on short wide images. You could dig into the math and see if you can spot the issue.
I can point you to the right part in the code if you'd like
VoidVolker
@VoidVolker
Jul 07 2015 16:48
Yes, do it please, I tryed to find by myself - but I notfound it )
In function, what calculate new position is need to add ( currentPosition % canvas.width ) - and it will not accumulate, also need to correct algorythm wich tilte need to draw
Funny thing is all three of them are if (!wrapHorizontal)
At any rate, that's a starting point
I think it does have to do with viewportTL and viewportBR...the tiles all seem to be in the right places, they're just getting cut off too soon.
Grant Echols
@gechols
Jul 07 2015 17:36
@avandecreme - live example of the tile loading problem: https://familysearch.org/reference/controls/OpenSDExample - try the 'Open Film' option and watch your javascript console.
VoidVolker
@VoidVolker
Jul 07 2015 17:39
@iangilman thx for the links, I'll chek it tomorow and try to do somthing
Ian Gilman
@iangilman
Jul 07 2015 17:40
@VoidVolker Awesome!
@gechols Interesting...everything looks like it's working properly, but I do get the errors in the console
Btw, the first thing that happens is a lot of index.xml files get loaded. You could speed things up a good deal if you loaded the info from all of those index.xml files in a single call to the server and then passed the resulting data into OSD
Antoine Vandecreme
@avandecreme
Jul 07 2015 18:05
I am not seeing anything in the console except SHA1 errors and some debug messages (OpenSD.openImages, clearImageViewer, fitting bounds)
ha actually seeing it on chrome but not on firefox
Ian Gilman
@iangilman
Jul 07 2015 18:32
@avandecreme I see it in Firefox too, but it doesn't happen until it looks like all the images have loaded on screen (later than I expected)
...and while I get the errors in the console, in the Net panel I'm not seeing any actual load errors, so that's interesting