Post #796: Hi there @roaoao ! Thank you for the follow-up and the useful tip
📋 Metadata
- Author: Pior
- Date: 2017-08-23 21:16:52
- Type:
feature_request - Quality Score: 8/10
🏷️ Tags
⚙️ Related PME Features
- Pie Menu Editor
- Panel Group Editor
- Menu Editor
💬 Content
Hi there @roaoao ! Thank you for the follow-up and the useful tips. The addon is truly fantastic, no doubt about it. I’ll make sure to gather my thoughts on it later once I have more mileage with it, as I think there are a few more little details that could improve its discoverability overall. There are also a few dangerous buttons that should definitely be labelled in plain text rather than being represented with a cryptic icon. Some buttons are also superfluous and could be removed altogether.
Basically the rule should be : the end user should never end up losing work by merely clicking around the interface. Of course it is sometimes possible to add a pop up warning for safety (like what you did when pressing the X button to delete all menus) but I think this is bad UX practice because error prevention should go one step further. The button itself should be labelled “delete all menus”, and placed somewhere in the UI further away from the more frequent operations and switches - probably grouped with the wide import and export buttons (which look fantastic in plain text !!)
Another rule : there is no point attempting to save space through tiny icons, especially if they make functions harder to understand than if they were plain text. You have the whole addon panel available for you to make the UI breathe, so don’t hesitate to space things out and use more clear buttons.
More about the X button to delete all menus with a warning : it is currently grouped with the + / - / New buttons, which of course do not require any warning because they are used all over Blender already. This is inconsistent. And this is precisely why I feel like text documentation is really needed : at the moment the UI is scattered with a lot of tiny cryptic icons, which makes the user (or me at least) very wary of pressing them, because I can instantly tell that the experience will be frustrating 
Lastly : what does the little “white paper sheet with a glowing spark” toggle button actually does ? Right above the star tag button, near the bottom left of the UI. It looks like a “new file” button to me, but it seems to hide or delete some menus.
This goes back to my earlier remark : pressing this button makes me feel like I am losing my previous work. As you can probably tell I am very passionate about clean, clear and concise UI with straightforward UX I’ll make some mockups later.
Regarding Dyntopo : is there a way to turn it on and off explicitly, rather than relying on the toggle ? Probably by adding some if/then/else to detect if it is mode is enabled in the first place ? I feel like this would be necessary for any macro involving this mode.