You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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__.
The text was updated successfully, but these errors were encountered:
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
inhv.core.traversal
and onNdWidget
inhv.plotting.widgets.__init__
.The text was updated successfully, but these errors were encountered: