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
Need a feature to set a minimum width for treemap block #7891
Comments
Hi @kundansonu Thank you for your suggestion. @jon-a-nygaard FYI |
This is thematically related to the column minPointLength option. It also comes with the same logical problems - what happens if many of these oversized items are positioned next to each other? |
This problem is in older versions as well. Any idea how this could be fixed in current versions, a temporary fix ? Also there may be cases when displaying 0 values is needed as well. |
Checked the forum and it seems there have been lots of requests for this feature since 2016 at least. And if I'm not wrong only fix/solution is to write a new algorithm based on the one we've chosen. |
Found a way, not ideal but works as a temporary fix. It will show 0 value boxes as well (all of them will have the 0.5 value size) and normalizes a bit the values with Math.log (for less extreme data could use Math.pow(val, 0.n)). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions! |
I am facing the same issue. Is there any resolution to this problem? |
Hi @ajankit85, |
Expected behaviour
There should be an option to provide a minimum block size
Actual behaviour
For a large dataset with few of records having a smaller value the block plotted on treemap is too small to interact.
Live demo with steps to reproduce
Please click on Europe and check for switzerland
I have changed the large tree map example and changed the value of Switzerland to 1
http://fiddle.jshell.net/s41m016L/
Product version
Highcharts JS v6.0.7
Affected browser(s)
Google Chrome, Firefox
The text was updated successfully, but these errors were encountered: