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.

Sign up for GitHub

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

Jump to bottom

Gauge with negative range does not work correctly #722

Open

blikblum opened this issue Feb 25, 2022 · 13 comments

Labels

blikblum commented Feb 25, 2022

Describe the bug
Setting a gauge chart with negative range ( scale: { min: -100, max: 100 }) does not show the correct position of clockHand. The drawing of bands also does not match the specified ranges

To Reproduce
Steps to reproduce the behavior:

Go to 'Example at CodePen'
Look at clockHand position (it should point to 0 but points to -100)

Expected behavior
The clockHand should point to the corresponding value defined in data series. The bands should visually match the defined ranges

Screenshots
I'm trying to implement Net Promoter Score chart like below. The values can be from -100 to 100

Desktop (please complete the following information):

OS: Windows
Browser Firefox
Version Latest

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
None

The text was updated successfully, but these errors were encountered:

Contributor

jwlee1108 commented Mar 2, 2022

Thank you for the issue. I'm going to fix it.

stale bot commented Apr 16, 2022

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Apr 16, 2022

The issue is still relevant

stale bot removed the inactive label

stale bot commented Jul 10, 2022

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Jul 10, 2022

The issue is still relevant

stale bot removed the inactive label

stale bot commented Aug 13, 2022

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Aug 13, 2022

The issue is still relevant

stale bot removed the inactive label

stale bot commented Sep 21, 2022

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Sep 21, 2022

The issue is still relevant

stale bot removed the inactive label

stale bot commented Nov 2, 2022

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Nov 2, 2022

Still relevant

stale bot removed the inactive label

stale bot commented Jan 8, 2023

This issue has been automatically marked as inactive because there hasn’t been much going on it lately. It is going to be closed after 7 days. Thanks!

stale bot added the inactive label

Author

blikblum commented Jan 8, 2023

Still relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment