I have an app thats ready for distribution. I've found some older documents on the subject, such as the "making a slick standalone," that proved useful but wasn't sure if there was anything that might be different now that it isnt listed in that doc.
1) The Max window could be hidden in the properties of the STANDALONE object and editing the JSON file. Does that disable the keyboard shortcut to open the max window?
2) I use some PATTR objects to recal informantion for MESSAGE objects that eventually passes to a THISPATCHER object... Should I be concerned that the user could edit the JSON or XML pattr preset files to be "script" or "thispatcher" messages that could potentially compromise my app or the code?
3) For Copyright protection I found ExcelSoftware to have some good options but in terms of online activation their monthly plans will eventually eat away at income. Are there any solutions to have online activation within Max MSP? MAXURL or JAVA object... with this it may be possible to make in-app purchases?
4) Is there something similar to OVERDRIVE option (Standalone Object property for audio) but for graphics? My max patch is quite large and my TIMECODE display from the TRANSPORT object does not render smaller units frequently enough. Miliseconds & Units just in increments of 5 hundred. Even when taken straight out of help file. Ideas?
Any tips for safe & protected standalone distribution appreciated. I hope Cycling 74' takes the step to deliver dependable documentation for this in the future.