These are chat archives for oxyplot/oxyplot

7th
Apr 2015
Øystein Bjørke
@objorke
Apr 07 2015 06:54
@stefan-schweiger ViewMaximum overriding AbsoluteMaximum sounds like a bug, please create an example and add to GitHub issues. It is possible that the ViewMaximum setter should be more protected (internal)
@Nyakoo right, the Value property is used for color coding. The Tag is not used, available for the user. To convert other item types to ScatterPoints, I think you can use the Mapping property in the ScatterSeries. PS. The forum may be a better place to discuss things like this :-)
Øystein Bjørke
@objorke
Apr 07 2015 07:01
@tjbobo I think Maximum and AbsoluteMaximum could be set by the user. ViewMaximum should only be set by the view (when panning/zooming, and should respect the AbsoluteMaximum). ActualMaximum should be calculated when rendering.
Øystein Bjørke
@objorke
Apr 07 2015 07:08
I want to raise the bar for the commit history on pull requests :-)
Stefan Schweiger
@stefan-schweiger
Apr 07 2015 07:35
@objorke so ActualMaximum should always return the maximum value of the actual data in the chart if available right? If that's the case I will create an issue for this later on ;)
Stefan Schweiger
@stefan-schweiger
Apr 07 2015 08:19
@objorke also I've now created a pull request for adding a mean value to the BoxPlot
Øystein Bjørke
@objorke
Apr 07 2015 10:34
@stefan-schweiger yes, the ActualMaximum should return the actual value as shown in the view.
Stefan Schweiger
@stefan-schweiger
Apr 07 2015 10:52
@objorke so it's depended upon the ViewMaximum?
Currently ActualMaximum is composed of either ViewMaximum, Maximum or the calculated maximum if the other two are not set. And ViewMaximum just gets used when the "default" view gets changed (but is also set-able from the outside (why?))
In my opinion ActualMaximum should be the actual calculated data maximum (+ padding) andViewMaximum the currently displayed maximum in the view (and should not be set-able from the outside).
The only two properties with public setters should be AbsoluteMaximum (which should be the max value for ViewMaximum) and Maximum (which should be the default value for ViewMaximum)
but that's just my two cents, as I guess this would include breaking changes for some people...so as said before, it would also be fine for me to just introduce a property called LockMaximum to disable to possibility to pan and zoom beyond the calculated data maximum.
Øystein Bjørke
@objorke
Apr 07 2015 19:58
@stefan-schweiger I think we should avoid a breaking change here. Can we continue this discussion in the issues section on github?
Stefan Schweiger
@stefan-schweiger
Apr 07 2015 22:47
@objorke ok, I've created #442 to discuss this issue further