Not all items in override UI always apply to visualizers

[jleibs]

The value shown can be confusing and the fact that modifying it does nothing is more-so confusing.

• Common issues that impact multiple archetypes:

  • Color shows up as white instead of previewing the resolved entity-hash color.
    • there's missing fallback providers (which we'd also ideally use, but that goes through annotation context resolve often, so exercise caution)
    • Fixed in Fix ui for color fallback showing the wrong value #6703
  • Many visualizers allow you to override Text, but it does nothing
    • today, we don't show labels after a certain hardcoded threshold. This is bad and needs fixing in general, but not now. Still open question whether this should be a separate visualizer.
    • consider disabling this for everything except plots
    • Fixed in Multiple instances of points/arrows/boxes with single label display label now at the center #6741
  • Radius shows 1.0 incorrectly making initial edit weird
    • Missing fallback providers
    • Part of Expose ui based radii, remove view default radius setting #6540
  • Drag to edit a float slider with negative values has too small of a velocity (observed with draw order)
    • fixed in Fix draw order slider moving too slowly when negative #6718

• Assessment for each visualizers:

  • BarChartView
    • Override color doesn't work
    • Tensor -> set to fallback value is "weird" but also doesn't work
    • Fixed in BarChartView now queries overrides & defaults #6717
  • Arrows2D
  • Arrows3D
  • Asset3D
  • Boxes2D
  • Boxes3D
  • Cameras
  • SegmentationImage
  • Image
  • DepthImage
    • FillRatio doesn't do anything in 2D view
      • in 2D we don't show the depth cloud which would be affected by this
      • documented better since Better document limited effect of DepthMeter & FillRatio in 2D views #6745
  • Lines2D
  • Lines3D
  • Mesh3D
  • Points2D
  • Points3D
  • Transform3DArrows
    • Kind of weird -- you can reset the Transform to the fallback value, but it has not effect.
    • Logged in Transform hierarchy is not affected by blueprint overrides #6743
  • Tensor
  • TextDocument
    • Setting MediaType to fallback application/octet-stream doesn't do anything. Still shows as Markdown
    • Editing the Text content does nothing
    • Fixed in Fix overrides/defaults not working in TextDocumentView #6714
  • TextLog
    • All overrides broken: both color and text can be overridden but do nothing
    • Fixed in Handle static text messages in TextLogView gracefully, handle overrides #6712
  • SeriesLine
  • SeriesPoint

• Other observations:

  • Overriding a color of a 3D asset in a 3D scene doesn't change it's color in the projection into the 2D scene. I know why this is the case, architecturally but as a user this feels somewhat unexpected.

[Wumpf]

left some notes from slack conversations on various items

[Wumpf]

Suggestions for resolving the label issue:

• link to an issue from Text component where we describe the issue in details
• document hiding behavior on Text component so it shows up on the tooltip (careful: it's used in places where this does not apply)
• maybe: increase hiding threshhold, experiment!

[Wumpf]

Suggestions for resolving depth meter issue:

• open an issue about problematic visualizer sharing between 2D/3D on the example of DepthImage. One solution is to split DepthImage (?) and DepthImage (or DepthImage2D/DepthImage3D). Another thread of solutions is "View in View"
• improve documentation on depth image archetype
• add note on FillRatio
• add note on limited effected of DepthMeter (it's not nothing, but close ;))

[Wumpf]

label was resolved differently, we now place single labels at the center of visualizations

[Wumpf]

all addressed, mitigated or filed separately!