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

truncate meta-recording labels #347

Closed
kdarras opened this issue Apr 5, 2023 · 3 comments
Closed

truncate meta-recording labels #347

kdarras opened this issue Apr 5, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@kdarras
Copy link

kdarras commented Apr 5, 2023

When the meta-recording boxes displayed in the timeline are too small for labels to appear entirely:
image

...the text should be truncated and appear entirely only when clicking the meta-recording boxes (or with mouse over) and the name of the recording too. If #217 is already implemented, the duty cycle should be shown too.

@kdarras kdarras added the enhancement New feature or request label Apr 5, 2023
@kdarras kdarras changed the title hiding meta-recording labels truncate meta-recording labels Oct 17, 2023
@kdarras kdarras moved this to To do in Recordings Dec 11, 2023
@kdarras
Copy link
Author

kdarras commented Feb 21, 2024

The truncation works well but it seems that recordings still have a buffer around them that prevents showing them one after the other at close intervals:
image
As you see on the image above, even though these are recordings of 900 seconds starting at the same daily time, they show up stacked on top of each other.

The purpose of this truncation issue was actually to make sure that the recordings are shown in one row for each site. I thought it was only due to the long, untruncated labels that were always shown, but realise now that it is due to something else underneath... could this be fixed?

If yes, then the minimum space between subsequent recordings should be null or minimized, instead of being (unnecessarily?) a few pixels wide like now:
image

For very close-by recordings, it would probably mean that we show only their border and that a thick bar of the same color as the border would appear. Maybe then the sound names should not be displayed (or a "several recordings overlap - zoom in") if several recordings overlap?

@kdarras
Copy link
Author

kdarras commented Feb 28, 2024

It took me some time to realise: your approach for clustering recordings on the timeline just like it is done for sites on the map is extremely cool!

To make it more intuitive for users, I suggest to show the number of recordings inside the cluster in bold font, with an underline, and clickable (for zooming in) with a single click instead of a double-click just like on maps.

Note that recording names stay expanded after clicking them to open in the player (they can vanish when playing with the mouse but I am not sure how exactly to hide them):
image
They should be collapsed instead, just like after the mouse is not hovering on them anymore, because this residual, invisible expansion also messes up the spacing between blocks afterwards:
image

Maybe the space tolerances should be adjusted a little as sometimes, zooming out (but sometimes even when zooming in) results in recordings being on top of each other when in fact they should be clustered:
Screencast from 28-02-2024 12:34:16.webm

There is a special situation where separate recordings from the same site and time become inextricably merged:
image
image
No matter how far I zoomed in, I could not open the individual recordings from the timeline because their time overlaps. However, it is possible to have multiple recordings from the same site (from multiple recorders) at the same time. In this case the separate recordings should be displayed on top of each other after zooming in, as there is no way to show them in one row.

Also, after adding 8 more recordings from 2016 to this collection, even though there are now 12 recordings inside, I could find only the 8 new ones on the maximally-zoomed-out timeline:
image

@kdarras
Copy link
Author

kdarras commented Mar 4, 2024

Excellent fixes! Just a minor point: maybe it would be better to show cluster numbers with a bold font instead of an underline, as the underline is too close to the number:
image

No need to re-test this. Working in Docker.

@kdarras kdarras closed this as completed Mar 25, 2024
@github-project-automation github-project-automation bot moved this from To do to Done in Recordings Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

1 participant