Persist `_enum_cb_cache` and `_str_cb_cache` in `BLField` #13

New Issue

Closed

opened 2024-05-04 16:49:14 +02:00 by so-rose · 0 comments

so-rose commented

2024-05-04 16:49:14 +02:00

Owner

The lack of persistence for the dynamic EnumProperty callbacks causes dynamic enums to severely break on startup if they cannot perfectly recompute.

There are many situations where the data might not be instantly available - lacking internet, file moved, etc. . Nodes ought to not fundamentally break when that happens. Persisting them doesn't solve the underlying problems, but it makes nodes that rely on dynamic enums far more robust, by guaranteeing that reloading Blender won't alter their state.

The lack of persistence for the dynamic `EnumProperty` callbacks causes dynamic enums to severely break on startup if they cannot perfectly recompute. There are many situations where the data might not be instantly available - lacking internet, file moved, etc. . Nodes ought to not fundamentally _break_ when that happens. Persisting them doesn't solve the underlying problems, but it makes nodes that rely on dynamic enums far more robust, by guaranteeing that reloading Blender won't alter their state.

so-rose added the

bug

architecture

labels 2024-05-04 16:49:14 +02:00

so-rose changed title from ~~Persisting `_enum_cb_cache` and `_str_cb_cache` in `BLField`~~ to Persist `_enum_cb_cache` and `_str_cb_cache` in `BLField`

2024-05-04 16:49:20 +02:00

so-rose added this to the Robust Simulation milestone 2024-05-07 10:06:41 +02:00

so-rose referenced this issue from a commit

2024-05-15 12:47:31 +02:00

feat: big refactor to fight fundamental crashes

so-rose closed this issue

2024-05-15 12:47:31 +02:00