Post #2350684

2026-03-30 03:45 UTC

@MikkoMononen@mastodon.gamedev.place @pervognsen@mastodon.social I think especially with that screenshot example of a gradient, an artist would appreciate marking the colours as overrides regardless of whether the base changes. The snapshot+flags seems like a good approach and the UI does well to make it clearer what is pinned in the derived data, but still not entirely obvious how the gradient works. I wonder if it would be easier to understand if you could flag entire blocks of data (the whole gradient).

Replies (1)

@MikkoMononen@mastodon.gamedev.place 2026-03-30 05:23

@idbrii@mastodon.gamedev.place @pervognsen@mastodon.social In my books the "mark entire block as overridden" goes into the "Hierarchical data" section, which I omitted :) With hierarchical data like nested structs or objects, it makes sense to allow you to say at any point in the hierarchy that this struct/object and anything below it is overridden. There are some cases where you may want to override the whole struct/object. For example, I think you should not override a component of a vec3 (and some people disagree with passion).

Open ##2350685