tabsel

Even though I own max quite a while now, I just recently try do gif into it. I want to develop a midi controller mapping/translating, with max receiving midi on one port and sending translated midi out another port.

The translator code will be written in JS, as it will be too complex. The UI part simply consists of a umenu for choosing the midi in port, and the umenu for choosing the out port. The patch will be standalone.

Now I want the patch to have its port settings persistent upon launching/quitting the standalone.

struggling-with-basics-data-persistence

well, this way, the midi ports are "hardcoded". I'd rather have the user choose from the ports available to the system (midiinfo -> umenu), with the ones the user chooses being automatically chosen the next time the users launches the patch...

 simple "Persistent umenu" that I will attach here. It only works if you "File > Save" your patcher.

This might be bad advice but... if your data is complex enough, maybe you should save all of your "persistent" data as an xml file. Then you could write/read the xml file using a closebang/loadbang every time it closes/loads. If you want to pursue the xml in Max thing then check out the "detox (jasch object)". 

I made a very simple "Persistent umenu" that I will attach here. It only works if you "File > Save" your patcher.

This might be bad advice but... if your data is complex enough, maybe you should save all of your "persistent" data as an xml file. Then you could write/read the xml file using a closebang/loadbang every time it closes/loads. If you want to pursue the xml in Max thing then check out the "detox (jasch object)". http://www.jasch.ch/dl/default.htm

Hard to get to know which objects are able to do what exactly, so that you get to know which objects to use.

Struggling with basics: data persistence