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

Brushing/filtering issue since 4.1.0 - Broken example #1881

Open
Frozenlock opened this issue Aug 11, 2023 · 6 comments
Open

Brushing/filtering issue since 4.1.0 - Broken example #1881

Frozenlock opened this issue Aug 11, 2023 · 6 comments

Comments

@Frozenlock
Copy link
Contributor

I'm updating from v3 to v4.
I've updated D3 to d3@5.16.0.
In the process of slowly increasing DC versions, I noticed a problem introduced in 4.1.0 which is still present in 4.2.7.

For brushing, the animation slows to a crawl.
It looks like the filtering function is being called continuously:

image

This video shows the speed of a normal filter, then of a ranged filter:

filter-problem.webm

Broken Example

It looks like the same issue is occurring with one of the examples:
https://dc-js.github.io/dc.js/examples/brush-ordinal-dynamic.html

@kum-deepak
Copy link
Collaborator

Many thanks for the detailed report. I will look into this.

@Frozenlock
Copy link
Contributor Author

Any news on this? My short-term memory won't be able to hold onto it for long... 😅

@kum-deepak
Copy link
Collaborator

I remembered seeing this issue a couple of years back on the same example. I checked my notes, and we had noticed it with a version upgrade of D3. With my limited knowledge of D3, I could not track down the underlying cause,

This example is convoluted, as it relies on the internals of dc. In the next version, dc is getting refactored significantly, which allows this feature to be achieved differently - actually far less convoluted (https://dc-js.github.io/examples/brush-ordinal.html). The new approach does not suffer from this issue. Unfortunately, that approach may not be implementable in the current released version of dc.

In summary, we do not have a solution for this issue for dc v4. For the next version, there is a better way that does not suffer from this issue.

We are targeting an alpha of the next version in a couple of weeks.

@Frozenlock
Copy link
Contributor Author

Thanks for the update!
Will the alpha version be announced in the changelog, or should I keep my eyes open for a particular branch?

@kum-deepak
Copy link
Collaborator

The issues are marked in a milestone - https://github.com/dc-js/dc.js/milestone/17

The branch is https://github.com/dc-js/dc.js/tree/dc-v5

We are currently looking for someone to check the migration guides, etc. Please let me know if you would like to participate.

@Frozenlock
Copy link
Contributor Author

I'm not sure I'm in the best position to spearhead any kind of transition; I'm on Clojurescript and I'm not fluent in Javascript. Still, when trying to migrate I will let you know if I encounter any pitfalls or bugs.

Looking forward for the next version alpha 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants