-
Notifications
You must be signed in to change notification settings - Fork 131
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
counter-clockwise gauge #220
Comments
Can you provice a graphical example about what you are looking for please? |
Thank you for your reply. The following is the URL of the sketch I uploaded https://pan.baidu.com/s/1V7Ap_iySwf1wZ10I8L99WA?pwd=7hxy input code: 7hxy |
Looks like I have only implemented it in the GaugeSkin.
|
Maybe my expression is not accurate enough. I want the value progress bar to express positive and negative through positive or clockwise.Now when the value is negative, the progress bar is always displayed at 0. |
1 similar comment
Maybe my expression is not accurate enough. I want the value progress bar to express positive and negative through positive or clockwise.Now when the value is negative, the progress bar is always displayed at 0. |
Maybe my expression is not accurate enough. I want the value progress bar to express positive and negative through positive or clockwise.Now when the value is negative, the progress bar is always displayed at 0.
链接: https://pan.baidu.com/s/1yD8hsbbbCpcQuCU0txP2GQ?pwd=kjgx |
Yes, I understand but it is not implemented in the BarSkin, so it only works in the GaugeSkin at the moment. Because I'm busy with other stuff, I won't have the time to implement it at the moment. But as mentioned for the BarSkin it should not be too hard to implement it on your own and either use your own skin based on the BarSkin or creeate a pull request which might end up in Medusa. |
Now, because of the value clamp,the gauge can only support clockwise graphical representation. When the value is negative, could you provide counterclockwise representation
The text was updated successfully, but these errors were encountered: