Persist _enum_cb_cache and _str_cb_cache in BLField #13

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

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
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: so-rose/oscillode#13
There is no content yet.