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

Handling widget sorting issues #1835

Closed
philippjfr opened this issue Aug 31, 2017 · 1 comment
Closed

Handling widget sorting issues #1835

philippjfr opened this issue Aug 31, 2017 · 1 comment
Assignees
Milestone

Comments

@philippjfr
Copy link
Member

In recent releases we introduced the option of having unsorted keys on HoloMap/DynamicMap. This works well but when creating widgets the keys usually still end up being sorted. This is because the code that computes the set of keys generally makes use of a NdMapping to help sort the keys, which destroys any sort order defined by the original mapping. The main issue here is that when the incoming keys are unsorted but there are multiple partially overlapping sets of HoloMaps/DynamicMaps the sort order needs to be resolved somehow and sorting everything is the most sensible approach.

We'll have to think a bit about how to deal with unsorted mappings and how that relates to a bunch of partial orderings that need to be merged. The two main instances where this is happening is in unique_dimkeys in hv.core.traversal and on NdWidget in hv.plotting.widgets.__init__.

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant