In GXT 3.0.2b, NumericAxis.setMinimum() doesn't work - minimum is always 0.
In GXT 3.0.2b, I have a bar (column) chart. I am setting the minimum of the numeric y-axis to 1, but still getting it started from 0. My y-values are in the range 0 - 63. So I need to see in the chart only bars for values greater than 1. Instead I see bars for all values.
It looks like the implementation of the method snapEnds() resets minimum (this.from) to 0 in line 364.
Would you also please make sure that setMaximum() works correctly. Currently, when I set maximum to 1 and then add value 10, the axis stops at 1 as expected but the bar doesn't stop at 1 - it goes all the way till the end of the chart area.
We've made a comprehensive set of changes, modifying the behavior of setMaximum/setMinimum, setSteps, and setInterval to try to make them more predictable and reliable. These changes are in SVN and the latest nightly build, and will be available in the next release.
The first change was to stop any 'pretty number' code when a maximum or a minimum is set on the NumericAxis. This enables developers to tie down one or both ends of the axis by specifying a specific starting or ending point - if a value is not specified (or is restored to the default NaN), the axis will use the data to find an appropriate value.
Once in this state, the number of steps (i.e. setSteps(int), defaults to -1) or the size of each step (i.e. setInterval(double), defaults to -1) may be specified to be followed. If the number of steps are given, the axis will use that to compute a interval size, based on the range (distance from min to max, described above), if not, it will use the given interval to compute the number of steps.
If no maximum or minimum are set, the step count or interval will be treated as a suggestion, not a requirement - without specified bounds, 'pretty numbers' will need to be generated, but we don't presently use a method that lets the step count/size override the bounds to generate good values. If both step count and interval are specified, step count will take precedence - it is contradictory to specify both when you can set the max and min and either step or interval instead. If neither step or interval is set but a max or min is specified, the axis will use place 10 steps between the maximum and minimum value as a default.