"Invisible" Max Window menu item in standalone
I would like to allow end users of my standalone to display the Max Window, but *only* using Command-M (Mac) keystroke; I do not want there to be a visible menu item called Max Window. I’m adept at modifying my standalone’s maxinterface.json file, which, if this is even possible, I’m sure will require customization of.
Anyone try this before?
Thanks, but I’m very familiar with that setting. What I’m after has to do with the visibility (or rather, lack of visibility) of the menu item that allows one to show the Max Window.
Sorry i understand now your question. is not possible using the maxinterface.json file? A friend of mine show me an application that use this kind of standalone. But i think that they didnt want to share the code.
Can you share a example of json file that you have created to learn more about it?
thanksss. I’ll investigate about it and if i find something i’ll comunicate to you.
You should be able to do it I think, the standalone maxinterface.json file should look like a stripped-down version of the regular one. In the past I managed to add a few custom menu items to the standard file (Hide on Lock and Show on Lock in the right-click menu), it was fun to fiddle around. (Though an interface to customize the file would be really cool…no worries about mis-typing etc.)
So if that worked, there should be a way to take out whatever menu items you want…? will take a look at home :)
Well, the contents of the maxinterface.json file that are relevant follow here:
"message" : "maxwindow",
"label" : "Max Window",
"target" : "max",
"shortcut" : "M"
So it’s easy to change the label to say something else, and that will work just fine. But I want to get rid of the "label" altogether, which so far does not seem to work. You cannot remove the label line completely, or make the label "" – the standalone (at least on a Mac) will still insert an entry in the menu (called "a command") if you do.
Dan, I’d recommend just zapping the entry altogether and adding a custom key command with the key object, using the modifier output:
----------begin_max5_patcher---------- 563.3ocyU0ziSCCD8bxuBqHzdpTkOZKTP6A9AfD2AzpIwSaM3XWYOosKq5+c rcZ5lzMHscWDhCMU9MOOYlmedxCwQIk5CnMg8A1WYQQODGEEf7.QmVGkTCGp jfMPKQg60k+HYRaHBOPAXKAJNH0JrKjfGB3H+1rNLUSsPIQJjprSfqzJRA0X f9mLBP1ittg53m1iuU7q.+r7ocvaApZiPs9NCVQscTQ96bgYYEdVrEK8OySm lx99o8XgcH+NWI51xc.QFQYC0pGQm6eWpM3pUBIdtJ+Lbfsf8EGLZPUkaGSN QEZ3BssY6Vsg50jtWEBlpMqzlZg05JSe9rCX.R4dghq2agJRrC60yQd8kZr6 DVQobXDNPPIXGB5NVPkUnUCeE5cngatL2UfhpjZKR5sRbGJCRIZFt2FK11Ct naFrekVpAdInVycBBPttaP7ZAWzWRBvGii6ddLdxqy7IVwdiHic6sr74KX2b iaUteUV5RFsAULesMhuLe9nFy7qzX1Yjagn62hs1ujjyFsmumcw7dV17rhG8 r+8zqeh2O1szwUizqTMl8mTCghRlL1eu.Up38dcYV3587kSm+JznZzZg03SD oO9MiiGy8q8VYGAoPgU5FE02pzWFm8eqoZQPuVFlCVTbgdERan6t36Ag74wG JhVciopqn57Or7yUGGstIAtoAZUOR9qbrGG.uQv4npuMyMp.bi3B5Y5nGmWU 8T7bpmr+I0yEs930i287hzG2Y4w3eyn7aSK -----------end_max5_patcher-----------
never mind…got it :)
Of course! Thanks for the alternate solution Ben!
Ben if you want to close the max window with a message?
Just out of curiosity, why might opening the Max window be available as a simple message, but closing it isn’t? Seems like the other windows (coll, text, pattrstorage, buffer) all have open and close (or "wclose") commands built-in. Something different about the Max window?
…this also applies to clearing the Max window contents programmatically…would be nice maybe…if not possible, wondering why :)
"…this also applies to clearing the Max window contents programmatically…would be nice maybe…if not possible, wondering why :)