Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Put your menu under Tools instead of at the top level #74

Open
JoeStrout opened this issue Feb 25, 2022 · 4 comments
Open

Comments

@JoeStrout
Copy link

We use a lot of 3rd-party editor extensions. If every one got its own top-level menu, I'd need a much wider monitor.

Many other 3rd-party tools put their menus under "Tools". (Examples: Odin Inspector, Graphy, Demigiant, Modern UI Pack). It'd be great if ParrelSync would be a good citizen and do the same.

As a workaround, I'm hacking the ParrelSync files and changing all the MenuItem attributes to include "Tools/". But of course I'll have to re-do that any time I update the package.

@JGroxz
Copy link
Contributor

JGroxz commented May 13, 2022

+1 on this.
Having multiple extensions in the project in the topmost menu makes it very cluttered. Moving ParrelSync under Tools would be a nice thing. Another alternative place for it is under Window, many 3rd-party extensions use it, too (Zinnia, UniTask, Mirage).

@314pies
Copy link
Contributor

314pies commented Jun 26, 2022

Thanks for bringing this up!
Anyone who also wants to move ParrelSync under the "Tools" menu, please leave a like or reaction so we know you like this idea :)

If people like this idea, we should be able to add an option to customize the ParrelSync menu item path in the future release.

@JGroxz
Copy link
Contributor

JGroxz commented May 4, 2023

Any updates on this? Would it be alright if I give it a go and make a pull request @314pies?

@varan941
Copy link

varan941 commented Jul 5, 2024

You could do it by yourself. Just find all strings "[MenuItem("ParrelSync" and replace them to "[MenuItem("Tools/ParrelSync" in your files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants