`ColorGrading` component cannot be fully edited

[eswartz]

What versions are you using?

Software	Version
OS	Debian Linux 13
Blender	5.0.1
Bevy	0.18
bevy_skein (Rust Crate)	0.5.0
Skein Blender Extension	0.1.15

Describe the bug
When I add the bevy_render::view::ColorGrading component, most of the structured content is not presented.

stderr for blender shows:

07:46.698  bpy.rna          | ERROR Python script error in SCENE_PT_skein.draw
Traceback (most recent call last):
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 432, in render_two
    render_two(layout.box(), obj, key)
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 418, in render_two
    if "PointerProperty" == value.function.__name__:
                            ^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'function'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 75, in draw
    draw_generic_panel(context, obj, self.layout, "scene", "SCENE_PT_skein_preset_panel")
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 211, in draw_generic_panel
    render_two(layout, active_component_data, hash_over_64(type_path))
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 435, in render_two
    render_two(layout.box(), obj, key)
  File "/home/ejs/.config/blender/5.0/extensions/user_default/bevy_skein/skein_panel.py", line 418, in render_two
    if "PointerProperty" == value.function.__name__:
                            ^^^^^^^^^^^^^^

To Reproduce
Steps to reproduce the behavior:

1. New Blender file.
2. In Skein panel, fetch remote types
3. Add the bevy_render::view::ColorGrading component
4. See error in stderr and incomplete UI.

Expected behavior
Expect to see several structured sections (global, shadows, midtones, highlights).

Screenshots

[ChristopherBiscardi]

This seems to be because we aren't handling Range, especially Range<f32> in this case. Type registry information for Range<f32> looks like it is opaque, so we'll have to code support for ranges explicitly, which we don't currently do.

  "core::ops::Range<f32>": {
    "crateName": "core",
    "kind": "Value",
    "modulePath": "core::ops",
    "shortPath": "Range<f32>",
    "type": "object",
    "typePath": "core::ops::Range<f32>"
  },

[ChristopherBiscardi]

In the meantime you can work around this by using a marker component (or a component that replicates ColorGrading without the Range) and using either an on_add component hook or observer to insert the "real" ColorGrading component.

[eswartz]

Thanks for the response! I already worked around it using a similar workaround.