Post #5617: I haven’t been in contact with roaoao recently, so the decision to require 5.0+
📋 Metadata
- Author: Pluglug
- Date: 2025-10-10 15:25:45
- Type:
discussion - Quality Score: 8/10
- Reply to: post_05615
- Replies (1): post_05627
🏷️ Tags
v1-20-x version-compatibility advanced
⚙️ Related PME Features
- Pie Menu Editor
- Property Editor
- Python Scripting
💬 Content
I haven’t been in contact with roaoao recently, so the decision to require 5.0+ is entirely on me.
That said, I want to clarify once again: PME-F is not diverging from the original PME. This is simply a practical decision to deal with 5.0’s breaking changes.
Supporting 5.0’s new property access system properly requires refactoring PME’s core architecture. Right now, we’re using bl_system_properties_get() as a temporary workaround (which is meant for Blender’s internal use). Maintaining backward compatibility with 4.x would drastically increase maintenance burden and complicate future updates. I’m not smart enough to handle that level of complexity.
Once the core is refactored and we can properly remove bl_system_properties_get(), lowering the minimum requirement again might become feasible.
Regarding PME-F safety: I believe it’s safe to use. I can’t guarantee it 100% (see disclaimer), but switching between PME-F and the official release shouldn’t make your house explode.
P.S. PME-F has already added one property for convenience, and I’m planning to add menu enable/disable states to the JSON export format. So there might be some minor friction when switching between versions. However, please trust that I’m committed to avoiding or minimizing any compatibility issues wherever possible.
❤️ 5 likes