Example how to add Plugin Commands to ribbon
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the existing PowerMill plugin examples and the plugin startup or load entry point. The issue does not name a file or test; done would be a documented or example-based way to create ribbon tabs, groups, and commands automatically rather than configuring them manually.
Written by the indexing model from the issue text.
Description
Hi there,
First off I would like to thank for all these very detailed examples for powermill plugins. I have been digging for some time thru them in search for some way to automatically add our plugin commands to the ribbon on startup.
Currently these have to be defined manually after plugin setup, using the "Customise ribbon" dialog, ending up creating New Tabs, New Groups and new commands.
Looking for details on how to create this stuff automatically on plugin startup / load, to end up with something similar like this (manually configured one):
Is there some way to automatically do this? It seems like I can only find solutions on how to add custom panes, which is something different I guess.
Thanks in advance!
Best regards,
Alex
- Dominant language
- C#
- Stars
- 25
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Autodesk/powermill-api-examples
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in Autodesk/powermill-api-examples
Similar issues
-
area-ai untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dotnet/extensions#7790 ·
Maintainers usually reply within 1 day
-
P2 testing
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
area-Infrastructure-coreclr os-ios os-maccatalyst os-tvos untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dotnet/runtime#134766 · 3 comments ·
Maintainers usually reply within 1 day
-
0 - Backlog Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
BrighterCommand/Brighter#4444 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day