This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Re-template RadialGauge to remove ViewBox (was: Setting RadialGauge Height and Width scales the text (Value and Unit)) #2246
Comments
Given the nature of the control, I don't think it'd be possible to keep the text of the value and unit at the configured text size. Maybe changing the design so that both the value and the unit are outside of the gauge, we could make them respect the text size regardless of the gauge scaling. Does this image reproduce the issue correctly? BTW, I couldn't get VS to recognize the header property, even with the packages from the 3.0.0 version. How did you use it? |
@Bmartin2013 Yes, the image is representative. The issue I have using the control as it is, is that 200x200 is too big for us and when I reduce the size to 150x150 the number becomes small, and does not go well with other controls.
Maybe, putting the text in the center and bringing it out of the About |
This control needs to be rewritten IMO, the entire layout depends on a single ViewBox that is causing these issues and needs to be removed. It's a breaking change, but I think it's for the better. Let's keep this issue open for tracking. Opening up to the community. (P.S. In the meantime, you could re-template the control in your app directly and remove any properties not needed) |
If this needs to be rewriten, @JerryNixon 's Speedometer Sample should be a good start |
@Bmartin2013 @nmetulev @avknaidu While we are at refactoring/rewriting I think following should be consider .
This is precisely I am trying to do. I am taking above as requirements and working on it. One thing that I don't understand is the UI automation. See this related question on stack. |
I'm definitely in favor of a more fluent default look and feel. After all, the current version was specifically designed for Windows 8. As far as templating concerns: it's easy to pull the text boxes out of the view box and override their font size (just did it: it still looks sharp at a size of 80). We could do this change in the toolkit, and add two more properties to the control: ValueFontSize and UnitFontSize. Initializing default colors from theme resources (including high contrast) is also something we could do. All default colors are hard-coded now. |
Whats the current status? |
Transferring this to the discussion as it requires more clarity. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I'm submitting a bug
Current behavior
When setting the Height and Width of RadialGauge to say 100,
Expected behavior
Value
andUnit
size should not change. Maybe it should also be possible to independently set font size for them if so desired.Minimal reproduction of the problem with instructions
Environment
The text was updated successfully, but these errors were encountered: