Skip to content

Update/tree map

Ghost User requested to merge update/tree-map into develop

Created by: S4K4YUME

Overview

  • moved Orientation enum
  • moved Bounds interface
  • added optional fields to support the visualization to the Node interface
  • added a pair of utility functions to better support changing the offset setting for the treemap
  • updated the logic regarding calculating the offset
  • updated the logic regarding calculating the bounds (without offset) as this was overcounting 1 element per sub-tree

Offset

I'm doing some 'weird' scaling, which probably could also use a translation in cases we're already zoomed in and the translation-coords for our view are not on the origin.

The reason to do this scaling is to support some meaningfull offset, whilst also keeping the visualization stable. I hope nobody is really offended by this solution (Though I myself am a bit.. :/ ), though I really would like to pull my hands off of this for now. It's been busting my balls and it would not be effective to continue and improve this.

Worst case-scenario, if it is really not compatible with some other future feature, then we can disable the offset (until it is fixed, if ever).

Image tax

image

image

image

Merge request reports

Loading