-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix(visualization) Clicking/touching a tile can sometimes redirect to missing data #185
Comments
I think in here somewhere is the need to be able to go to the 'next' recording from the listen page. Exactly what 'next' means is not clear - perhaps prev and next in terms of audio recordings could be chronological order of recordings in the site (which would be transparent to the user - they wouldn't know it was a different recording)? If prev and next was available over recordings, then it wouldn't matter about two or more recordings in an hour - pressing next would get there eventually. |
yeah that's along what I was thinking - particularly the new enhanced nav bar on the listen page would show 24 hours around your current position, at the current site only... which allow a pundit to skip recordings |
An enhanced fine-grained nav UI is definitely needed. i'm not sure what form this would take, but it could be as simple as pre-populated drop-downs or locking on to particular points in the dragable bar to aid in understanding the half minute segments available. |
well i was thinking of simply reusing the distributionOverview - it is adequate and already made It would also be an ideal place to try out the polynomial time scale idea |
👍 to between 1 minute and 24 hours around current location at current site only. |
Currently, the click resolution in the visualization strip is 60px - the same size as the image tiles - which means a click essentially represents clicking somewhere in that 60mins.
Current behaviour is to index into start of hour long block.
This behaviour can lead to faulty redirects - particularly at edge cases like:
It leads users to pages with no audio and no error message - very bad.
Present suggested solution is to smartly index into where we know there is data and then rely on (a yet to be) enhanced navigation bar in listen interface for fine grained navigation.
This will be sufficient for most cases, however for cases where:
which recording do we navigate to?
Suggested solution means that there would be essentially some files we could never navigate to. Opinions @jwim1, @cofiem ?
The text was updated successfully, but these errors were encountered: