Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
|
352 KB
|
|
140 KB
|
|
100 KB
|
|
31 KB
|
|
334 KB
Hang cleared. Change also fixed existing singleTick dim/reference issues.
@sachin: In the axisRenderer, there is a loop for tick locations that uses axis subdivisions. In the above scenario, there was confusion about the actualMax and actualMin of the axis because of the parameter value and the fact that there was a single tick. The subdivision count, normally very small (10 for example), was gigantic (~10e7). The reference scaling in DimAxis now corrects actualMax and actualMin rather than min and max.
I am also checking in some fixes (v18) to various min and max scaling issues today tied to the default values of refMax and refMin. They now default to Double.NegativeInfinity and Double.PositiveInfinity to insure that any incoming valid value will replace them. So there is no hang in v18 locally.
@sachin: In the axisRenderer, there is a loop for tick locations that uses axis subdivisions. In the above scenario, there was confusion about the actualMax and actualMin of the axis because of the parameter value and the fact that there was a single tick. The subdivision count, normally very small (10 for example), was gigantic (~10e7). The reference scaling in DimAxis now corrects actualMax and actualMin rather than min and max.
I am also checking in some fixes (v18) to various min and max scaling issues today tied to the default values of refMax and refMin. They now default to Double.NegativeInfinity and Double.PositiveInfinity to insure that any incoming valid value will replace them. So there is no hang in v18 locally.
There is no hang for min and max, but if the filter bounds meet in the middle, there can be a hang depending on the order of operation. Addressing.
@sachin: new scenario is not a hang. If user drags lower limit to meet upper limit at some intermediate value, allows snap to occur and then moves mouse further without dragging limit point, the chart does not render. There is no hang, however. The limits can be moved again to re-render chart. Happens even if no refline is present. Also occurs in v16. Is this a known bug? [see mov].
There is no hang for min and max, but if the filter bounds meet in the middle, there can be a hang depending on the order of operation. Addressing.
@sachin: new scenario is not a hang. If user drags lower limit to meet upper limit at some intermediate value, allows snap to occur and then moves mouse further without dragging limit point, the chart does not render. There is no hang, however. The limits can be moved again to re-render chart. Happens even if no refline is present. Also occurs in v16. Is this a known bug? [see mov].
Verified in 18-dev-38.Chart is generated if reference line is applied on date parameter & filter is set to max value.
Refer attachment(14243_18-dev-38.png,14243_18-dev-38.vizx)
Verified in 18-dev-38.Chart is generated if reference line is applied on date parameter & filter is set to max value.
Refer attachment(14243_18-dev-38.png,14243_18-dev-38.vizx)
Issue #14243 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 17.0.0-4, 18-dev-37 |
| No time estimate |
Hang cleared. Change also fixed existing singleTick dim/reference issues.