-
Notifications
You must be signed in to change notification settings - Fork 20
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
readme to explain repo usage #17
Comments
Hi Hannes, That's a great point... basically a repo is a directory where you can put python scripts (o mel files if you feel so inclined) that then will be available from the quicklauncher menu automatically. Let's say you add a This is really the most useful way to use quicklauncher imho, as it allows you to personalise the usage beyond vanilla Maya. Depending on your workflow (or where you work), it's very likely that you have to hunt down in the GUI the many custom tools written in python required to do the job, and what better way to do this than actually nor hunting down for anything and just type the first few letters of your custom script launching the thing. Does it makes sense? |
yes that makes sense |
i guess ideally every plugin has a MpxCommand, which would be auto exposed in maya.cmds., so auto added to the quicklauncher. |
The world is a wonky beautiful place 🙃 In the meantime, the repo feature supporting custom scripts helps users living in an imperfect world to build a nice-ish workflow having the tools they use all the time at their fingertips. |
hi
i haven't made the time yet to look into the code what repos do exactly. only saw the
dir(maya.cmds)
bit so far.i assume it's custom commands from a folder.
It d be great if you could find some time to add a quick brief to the readme on what repos do and how to use them.
and any limitations? like multiple repos at same time?
great little tool btw :)
The text was updated successfully, but these errors were encountered: