Hi Michael, thank you for the fast response!
Changing the registry also needs admin rights here, so it's hard to do "on demand" without having IT involved every time.
#1 a command line option for starting Moi would be amazing!!! My env variable suggestion is basically the same thing. I'd just love to set the path to the key file before launching Moi.
With this one could have a few license files in a network share and let the user choose one with a custom launcher.
#2 Yep I figured it's just a text and what I mean with "check" is basically already there I think (correct me if I'm wrong)
When 2 instances are open on different computers, Moi complains ( rightly so ) that the license is in use.
What I suggested is to allow having more than one key string in the key file, each on a new line.
Then Moi could loop over them until you finds an unused key. This might be hard to do as each instance would have to know it's used key, so yeah you'd basically mimic a license server here :/
Or as an easier and faster alternative: check validity of all keys ( e.g. 3 valid keys in key file ), then compare against number of moi instances running in the network and pointing to the same key file ( e.g. just 2 -> good to go)
This might be much easier to implement without breaking compatibility with current installs, since everyone has just one line in the key file right now => one instance allowed.
Also no need to change how you enter keys or anything, just a possibility for pipeline guys to do their thing.
#3 That would also be great, but a multi key solution like #2 might be more flexible for smaller studios.
~ Mariusz
|
