Copyright (c) 2022
The MIT License (MIT)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
2011, 2010, 2009, 2008
2011 issues being investigated
|Submitted by:||Sebastien Paviot|
It seems first that the hard crash of Maya is caused because the various internal variables of the script (stored in the preferences) weren't carried over to 2011 properly after the install procedure?
But that's just the beginning; many of the functions aren't doing what they are supposed to do, probably because of the change of python's version and its implementation with Maya.
I'll have to make a more major overhaul than I expected, especially regarding some weird UI warnings about flags I wasn't even using. I might have to rebuild it entirely in Qt and break the retro-compatibility altogether.
Furthermore, no clue if that will happen during the demo 30 days eval period lol.
anyway, we'll see.