4.3 Compatibility & Editable Hotkeys #1
No reviewers
Labels
No Label
bug
duplicate
enhancement
help wanted
need info
not a bug
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: extensions/space_view3d_pie_menus#1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "demeters_branch"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Preface: I got commit rights from Dalai by asking. As far as we know, this add-on has no active maintainer. I asked Nick Berkley for review, just so I don't YOLO push my first contribution. But in the future, I'd like to take over maintenance of this add-on, which I've been using for many years, although I always felt like it could be a lot better.
There are only two commits in this PR, and it could be split into two separate PRs, but I I don't really expect anyone to have time for actual code review, and I wanted to keep things speedy.
4.3 Compatibility
Since the brush system was changed in 4.3, the brush pie broke. I restored it to its original functionality by taking the old brush icon .dat files and packaging them with the add-on. There is also backwards compatibility (one if statement), so users who want to stick to 4.2 LTS can get future updates.
Hotkey UI
It was previously not possible to edit the hotkeys other than disabling them.
I lifted the hotkey system from my add-on CloudRig, which allows editing the shortcuts. Some shortcuts that were previously only 1 entry are now 2 entries (one for each context that the hotkey is available in.)
I also fixed the Alt+Space manipulator toggle not working due to a typo, and changed some UI strings to be more consistent.
I have nothing to do with this add-on but just a few UI thoughts:
LOOP_BACK
, notBACK
.For example:
Nice to see people keeping old add-ons alive.
Code is very good. Tested a bit, and everything works as well, except I get one error in mesh edit mode select menu (A), where it has Select Camera, and operator fails because
bpy.ops.object.select_all
expects object mode. Probably missed poll to remove that operator from edit mode.I'm usually not in favour of add-on checking for Blender versions and trying to accomodate multiple ones, but
if 'asset_activate' in dir(bpy.ops.brush)
is cheeky check, I like it. In general, because on extensions platform you can set maximum versions it is always best I think to increase minimum version for new versions when they need it, and change the maximum for previous one, and each Blender version gets its own version.There are some other authors in removed bl_infos that would be good to include in copyrights in blender_manifest, and yourself too.
@ -31,3 +20,4 @@
dirname, base_name = os.path.split(bpy.data.filepath)
base_name_no_ext, ext = os.path.splitext(base_name)
match = re.match(r"(.*)_([\d]+)$", base_name_no_ext)
Extensions review tool raises flag for this line
I'm not familiar with re module so can't help you with that much, just letting you know.
\d is a notation in RegularExpression denoting an integer (0-9), so I think this is a false alarm.
@ -117,0 +105,4 @@
)
op.asset_library_type = 'ESSENTIALS'
op.relative_asset_identifier = (
"brushes\\essentials_brushes.blend\\Brush\\" + brush_name
Non-portable backslashes here as well. Causes incorrect filepaths on some systems.
Use
os
here and let it handle thatNot sure but I THINK it should recognize blend file as a directory, I remember that being the case.
Great point, fixed!
5a061ca732
toaa3bc281a8
aa3bc281a8
to145b448875
Addressed all feedback so far, updated task description accordingly. Thanks a lot for the testing and feedback, guys! I wasn't expecting it! :)
All fine by me. Thanks for taking care of this
145b448875
to8cc8b274ca