FriFlo

I recently created a standalone app, but the the command+S option is greyed out and not available there.

First, how can I enable that for the standalone app? And what will it save? Would it be possible to automatically save a pattr-storage, that lives inside the app? I figured out how to program a button in the app, to save or load that preset to/from a specified disk location. I also know how to let the app automatically load that *.JSON file on start via a loadbang. But would it be possible to make the saving happen via Command+S?

I recently created a standalone app, but the the command+S option is greyed out and not available there.
First, how can I enable that for the standalone app? And what will it save? Would it be possible to automatically save a pattr-storage, that lives inside the app? I figured out how to program a button in the app, to save or load that preset to/from a specified disk location. I also know how to let the app automatically load that *.JSON file on start via a loadbang. But would it be possible to make the saving happen via Command+S?


saving-preset-automatically-with-commands-in-standalone-app

The easy way is to use the [menubar], but this way can only use the "saveas" command. My approach is to mess a bit with the "maxinterface.json" of the 

 afater it is built. It is located in the "resources/intefaces/maxinteface.json".

- open the "maxinterface.json" and find the following (just search for "customsave"):

        {
            "message" : "customsave",
            "label" : "Save",
            "navkey" : "S",
            "target" : "menubar",
            "shortcut" : "S"
        }


- Change the target value from "menubar" to something else e.g. "saveHandler"

- Find the "customfilemenu" and make sure that the the "customsave" is there instead of the "windsave".

- In your patch, you should have a [receive saveHandler], or the the word you choose for the target.

- In your patch, you should also have a [menubar] that is "enabled" (meaning, send a "1" to it).

Now, when the "Save" is triggered, either by clicking File->Save, or jsut Ctrl+S, the [receive saveHandler] will get a bang... so do the saving!

Just to be clear, you don't have to name it "saveHandler", just use the same name as the "target" value and the [receive] name.

If you do the same for the "close" or "saveas", make sure you 

Hope I'm clear and haven't forgot anything...!

The easy way is to use the [menubar], but this way can only use the "saveas" command. My approach is to mess a bit with the "maxinterface.json" of the standalone afater it is built. It is located in the "resources/intefaces/maxinteface.json". 

The way you can do it is the following:
- open the "maxinterface.json" and find the following (just search for "customsave"):

- Change the target value from "menubar" to something else e.g. "saveHandler"
- Find the "customfilemenu" and make sure that the the "customsave" is there instead of the "windsave".
- In your patch, you should have a [receive saveHandler], or the the word you choose for the target.
- In your patch, you should also have a [menubar] that is "enabled" (meaning, send a "1" to it).

Now, when the "Save" is triggered, either by clicking File->Save, or jsut Ctrl+S, the [receive saveHandler] will get a bang... so do the saving!
Just to be clear, you don't have to name it "saveHandler", just use the same name as the "target" value and the [receive] name.
If you do the same for the "close" or "saveas", make sure you remove the items from the [menubar] script.

Hey Nikolas, that looks exactly like what I am looking for! Thanks! I am going to try that out.

Hey Nikolas, that looks exactly like what I am looking for! Thanks! I am going to  try that out.


Saving preset automatically with "Command+S" in Standalone App?