According to previous posts, I was under the impression that you couldn’t include() a .mse file in another file, yet it seems to be working for me (unless I’m overlooking something silly).
Anyone else know about this?
Also, I have a rather large tool, with tons of fileIn() and include() statements, and I’m wondering do I have to convert all .ms extensions to .mse extensions in my fileIn() and include() statements in order for the encrypted files to be read in? I’m not done with the tool yet, but I’d like to test periodically that it works when encrypted, and I really don’t want to have to manually replace extensions every time. Are there any slick ideas for doing this easily?
Thanks.
I wrote a tool ( a maxscript ) which searches the whole projectfolder and subfolders for *.ms files. It gathers them, parses them for “include …” and “expands” those includes to the actual content. Additionally it appends all those scripts into one large script, writes that out to a new file and encrypts it. So the final encrypted release build of multi-file projects only takes one run of a maxscript now and the final install is only one *.mse ( plus a macroscript ). I guess that only works that good, because i use a strict regime of structs in my code and only one masterscript that contains all the “includes”
If you want i could post that build script, but i cannot give a guarantee that it will work for you…
Thanks, Josef, I would appreciate having a look at that code. I had thought about doing that myself, but I was hoping to avoid it! Having your script available will help me make it easier.
Regarding my first question, it appears that include() now works with .mse files, is that your understanding as well?
Thanks!
Josef, never mind on that maxscript, I’ve just done some more testing on Max 2011 through 2014, and in all those versions inlcude() works with encrypted .mse files, so I don’t need to compile all scripts into one now (although that’s a really cool idea).
Thanks,