oh, about the screenshots. If the rig is encapsulated in a black box, maybe
it would be possible set a callback preventing from unlocking the blackbox?
That way you can check want is inside and take screenshot.
El lunes, 6 de septiembre de 2021 a las 22:02:29 UTC+2, Rudi Hammad
escribió:
>
Quick question, I haven't use mel in 4 years now so it is probably
something foolish but why is this not working?
string $toEval = "def foo():import uuid; macAddress = uuid.getnode();
return macAddress; foo()";
string $macAddress = python($toEval);
print $x;
I would expect $x to print my
Marcus, thanks for your comment!
When I talked about export I meant not to ma or mb, I meant for example to
alembic or other, because as I knew alembic export is like a separate
plugin, and .correct me if I am wrong export to alembic will be ignored by
this callback.
I've not understood you,
The part of Maya that does the serialisation to ma and mb - be it via
export or save - is a singular point of access. The scene callbacks should
account for all ways in which creating those is possible, including via
Python and MEL. It wouldn’t account for manual export to other formats, but
It is a very interesting discussion.
Yeah, I will agree that it definitely must be invisible - so artists don't
even know that encryption happened.
But you can't stop on scene saving and loading, you should create lots of
workarounds in this "secure Maya client".
Somehow you need to lock any
And additionally, if in your scene you will have references,
during reference load you will need to decrypt this data,
the same will go to any geometry\textures or any files - you will need to
decrypt on the run.
And all of it must be done recursively on the whole data tree in scene,
so at some
It is a very interesting discussion.
Yeah, I will agree that it definitely must be invisible - so artists don't
even know that encryption happened.
But you can't stop on scene saving and loading, you should create lots of
workarounds in this "secure Maya client".
Somehow you need to lock any
