{"push_id":798890973,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"6a3d6f6335271765305d4cb38b940fba666c3837","before":"c86aae74f57147d964cfc3d8e748e580353005c7","commits":[{"sha":"ba2166ddb6993140fe2f3b099365fa11001f711a","author":{"email":"6dd62f145d8af7260c17657626b6222a91109c74@gmail.com","name":"robsgithub"},"message":"Mel Script workflow\n\nAfter some trial and error I was able to get the toolbox to call our\nthird part mel scripts without having to move any additional files on\ninstallation.\n- I moved all of the mel scripts to a mel scripts folder inside a new\nMelScripts folder in Utilities\n-Im generating and storing the path to this folder in the loadtoolbox.py\nmodule- Its value is based on wherever the toolbox folder is\n-To make any mel code work via python we will need to add the line\n\"from pymel.all import *\" to our initial calls. Ive updated this in the\ndocumentation\nEven though we call that command in most of the scripts it still needs\nto be called by maya in order to recognize it at call time in maya\nUpdated the rigging ui with a working call to the rivet script. Its\nworking great, we can use that command as a template if we want to use\nmore mel scripts","distinct":true,"url":"https://api.github.com/repos/robsgithub/toolBox_Repo/commits/ba2166ddb6993140fe2f3b099365fa11001f711a"},{"sha":"6a3d6f6335271765305d4cb38b940fba666c3837","author":{"email":"6dd62f145d8af7260c17657626b6222a91109c74@gmail.com","name":"robsgithub"},"message":"Slight Modification\n\nMoved some lines from  loadModule, to functions, code works the same,\nonly dif is  you wont have to swap out the custom loadToolbox.py files\nin your current installs like I though we would.  All changes should\nsync properly on next sync.","distinct":true,"url":"https://api.github.com/repos/robsgithub/toolBox_Repo/commits/6a3d6f6335271765305d4cb38b940fba666c3837"}]}