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

2055 old values not scaled #2092

Merged
merged 5 commits into from
Feb 15, 2022
Merged

2055 old values not scaled #2092

merged 5 commits into from
Feb 15, 2022

Conversation

msevestre
Copy link
Member

I feel that I am patching a leak with some tap but it's better than nothing..

@msevestre msevestre requested a review from Yuri05 February 9, 2022 13:28
ExpressionValue,
RelativeExpressionNew,
Unit
public static string Container = "Container";
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I created those so that we could remove the .ToString() used EVERYWHERE!!

};
}

private int getPercentageMax(DataView dataView, string columnName)
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the change. Instead of setting the max to 100, I set the max to the max value in the column (int) and then this will be used as max for the repo. The scaling is then done automatically

@msevestre
Copy link
Member Author

@Yuri05 This cannot be tested, unfortunately. Everything happens in the view.

@msevestre
Copy link
Member Author

and this?

@msevestre msevestre merged commit a893355 into develop Feb 15, 2022
@msevestre msevestre deleted the 2055-old-values-not-scaled branch February 15, 2022 16:33
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

Successfully merging this pull request may close these issues.

2 participants