We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Feature idea.
Sometimes it would be handy if dataset ID in change detection graph is displayed in all tool-tips (not just these where change was detected).
Imagine situation as on screenshot below where you might want to delete first two data points, but I do not see a simple way how to get dataset ID:
Also would be cool if I could somehow copy the ID or follow the link to it. Right now I can not select anything in the tool-tip.
Of-course I can just go by date, so not a big deal, but it feels bit fragile to me - especially if I need to copy&paste it just by my brain&fingers :)
Describe the solution you'd like
Some simple way how to learn dataset ID for any point in the change detection graph: maybe add dataset ID to tooltip and make it clickable?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Feature idea.
Sometimes it would be handy if dataset ID in change detection graph is displayed in all tool-tips (not just these where change was detected).
Imagine situation as on screenshot below where you might want to delete first two data points, but I do not see a simple way how to get dataset ID:
Also would be cool if I could somehow copy the ID or follow the link to it. Right now I can not select anything in the tool-tip.
Of-course I can just go by date, so not a big deal, but it feels bit fragile to me - especially if I need to copy&paste it just by my brain&fingers :)
Describe the solution you'd like
Some simple way how to learn dataset ID for any point in the change detection graph: maybe add dataset ID to tooltip and make it clickable?
The text was updated successfully, but these errors were encountered: