1.0.0.0 RC1 Miscellaneous issues

[Daniel Marsh-Patrick]

• Functionality tests in Service and Desktop for compiled package
• Test output in:
  • Android app
  • Windows app
  • IOS App (iPad; no access to iPhone)

---

Observations

• All but the first category colours appears to be reset or assigns it to a later category when testing on other dev machine
  • Seems to be something to do with sort order
    • If sorted by category then it just resets
    • If sorted by default (value) then it will just assign later on (if there are enough categories)
• Sorting is really unpredictable, presumably because how we're mapping the data
  • Modify to have sorting as an option in the properties pane
  • Only show if there are categories to sort
  • Offer options other than category
• When clamping the min/max at low resolution, the KDE doesn't always extend to this amount
• Tooltips don't mirror the y-axis units if changed. This needs to be investigated
• With the census data (lots of records, we get a dark gray background of 119,119,119/ #777777 with the y-axis render. Was an issue with stroke-opacity.
• The visual misbehaves when loading more rows and we have colour by category enabled (breaks the property pane and dispays an error), as well as sometimes not triggering when resized after this occurs.

[Daniel Marsh-Patrick]

The colour issue has been solved by tweaking how the object gets assigned for categories in the data view.

[Daniel Marsh-Patrick]

Sorting has been added and works pretty well!

[Daniel Marsh-Patrick]

For now, I'm going to remove clamping from the capabilities, and re-jig the enum for resolution, as low is far too low - we'll just leave standard, high and very high for now.

We can revisit both options later on if needs be.

[Daniel Marsh-Patrick]

I have implemented some options to show data limit overrides if there is more data to load, and this largely works with the exception of the issues highlighted above. Given the memory leak issues in 1.x and that fetchMoreData() is broken in 2.1 and 2.2, I've opted to add a setting to hard-disable the feature until the API is more stable.