Select your armature from numerous objects easily.
Panel : View3D > Sidebar > ArmPie > ArmaturePicker
Features :
The Solo Pie allows you to toggle bone collection solo using a pie menu. Only BoneCollections are titles (and their children) will appear in the Solo Pie, keeping the pie menu clean and easy to use.
Panel : View3D > Sidebar > ArmPie > Solo Pie
Solo Settings are used for configuring the Solo Pie and Show Panel. Settings
You can change the keymaps of panel calling for your special workflow.
Default Keymaps
Solo Pie : Ctrl + Right Mouse
Armature Picker : Shift + 1
This extension does not require special permissions.
Hey everyone,
Just a heads-up about a recent change regarding the licensing of add-ons on the Blender extension platform. Moving forward, all add-ons will need to be released under the GNU/GPL 3.0 license (SPDX:GPL-3.0-or-later). This is mainly to keep things simple and consistent across the board.
Previously, we accepted various licenses as long as they were compatible with Blender’s distribution. However, to avoid any confusion and streamline the process, all add-ons using the bpy API should now be presented as GPL 3 (the same license the Blender bundle is distributed). Regardless of whether the original code was under GPL 2, or something else like MIT or ZLIB.
Existing add-ons versions won't be affected. However, new updates will need to comply to the revised requirements.
Thanks for understanding, and feel free to reach out if you have any questions.
Python: Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\blender-4.3.0-alpha+main.8f996f178604-windows.amd64-release\portable\extensions\user_default\armature_pie\bone_collection_pie.py", line 238, in poll
return context.object.type == 'ARMATURE'
^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'type'
This error appears without active object in the scene. Whenever you have poll for context.object.type (or some other property) first you need to check if context.object (or active_object) is there at all. Only after that one is passed should you check for type. Correct this everywhere you may be using similar polls.
output\armature_pie\source\armature_picker.py:44:41:
Objs = [[Obj,Obj.hide_viewport] for Obj in bpy.data.objects if Obj.type=='ARMATURE']
output\armature_pie\source\armature_picker.py:80:41:
Objs = [[Obj,Obj.hide_viewport] for Obj in bpy.data.objects if Obj.type=='ARMATURE']
Here instead of iterating over bpy.data.objects
iterate over context.scene.objects
so that it limits search to active scene.
Tooltips are missing everwhere or are not useful. In armature picker UI for example three dots says "is_hide_others" and gear just says Armature Picker Enum. None of them tell me anything. Please go over your properties and operators and provide good descriptions for users.
Is there a reason you're not using default presets menu that Blender built-in panels use? Like "Format" panel in output properties? It seems to me like you're reinventing a wheel little bit and it feels off when something that users expect in one place is in another, but maybe I'm missing something?
--
I'm not sure what triangle icon button does in Bone Collections Show? Is it supposed to be "soloing" collection in the UI? tooltip is very confusing.
Behavior in pie menu is very weird. I have three collections added, first I solo one (left leg), and then when I call the solo again and choose right leg everything is hidden. It does solo right leg I can see it in properties panel, but I think it forgets to unhide something? Because this is not useful at all. I have to call "Un-solo all" each time to change what I'm soloing. Can you explain this a little more?
Also positioning is not optimal. Adding 3 items with default position settings overlaps un-solo buttons on top of them, and is very easy to miss and click something else accidentally. (https://imgur.com/EDXYg7R)
I'm also not sure what "Display Settings" is supposed to do? Choosing it in pie menu doesn't do anything.
Overall this is very good tool, or direction and design is nice. I would advise you on more things to make it more "Blender-y" and user-friendly.
You can look into my Keymesh add-on if you want to see examples of how they're done. 3. In overall, I suggest you follow Blenders UI guidelines: use property split, don't put more than 1 or 2 properties on single row (so panel doesn't have to be expanded), use correct uppercases and etc. It would stand out less from overall design.
Do make sure to update the license when you upload new version (and tag "Awaiting Review")
Sign in to comment.
Ready for review