MAX.XAM

In my standalone I am wanting to give the user the option to select several different UI colors (at least 4), but I want the last selected color to be the color that is loaded the next time the user closes and reopens the standalone. Ideally I want all of this done behind the scenes. No extra windows or dialog boxes to be displayed. I was messing around with pattrstorage and autopattr, but it is not clicking for me on how to have the last swatch color be auto loaded. Any help is appreciated.

preset

number

prepend

swatch

panel

In my standalone I am wanting to give the user the option to select several different UI colors (at least 4), but I want the last selected color to be the color that is loaded the next time the user closes and reopens the standalone. Ideally I want all of this done behind the scenes. No extra windows or dialog boxes to be  displayed. I was messing around with pattrstorage and autopattr, but it is not clicking for me on how to have the last swatch color be auto loaded. Any help is appreciated. 

Hey all,
In my standalone I am wanting to give the user the option to select several different UI colors (at least 4), but I want the last s

how-do-i-auto-load-the-last-swatch-color-selected-after-closing-and-re-opening-a-patcher

The swatch thingie is not automatically included in preset data, but you can add it by attaching a pattr object to it. See the pattr help page.

In any case, you'll have to save the swatch state to a file. You can use the pattr system and save the preset file with pattrstorage, or you could even save just the swatch color into a coll and reload when you open the patch.

Okay, here is what I have after going to coll route. It is hacked together and almost works ha! See attached patcher. My approach -

1. The preset object has 4 stored swatch colors. Selecting a preset will trigger the following

- color value sent to a message and a prepend 1 message is triggered to send that color value to the coll and the color value is stored in slot 1 of the coll object.

2. Directly after step 1 - coll is cleared and then writes that color value to a file (UIrecall). File is created with the correct color value save in line 1.

3. I have a loadbang set up to send out the color value save to slot one of the UIrecall file. This is where I am running into a problem. See step 4.

4. I select any one of the four presets and then close and reopen the patcher. The color that was used at the time of saving the patch is loaded rather than the color value in line one of the UIrecall file.

With each new preset selection the UIrecall file is cleared, a color value is written into slot one, and the ui preset file is saved. Like I said this is a hack job, but I'm close. HELP!

Okay, here is what I have after going to coll route. It is hacked together and almost works ha! See attached patcher. My approach - 

1. The preset object has 4 stored swatch colors.  Selecting a preset will trigger the following
- color value sent to a message and a prepend 1 message is triggered to send that color value to the coll and the color value is stored in slot 1 of the coll object.
2. Directly after step 1 - coll is cleared and then writes that color value to a file (UIrecall). File is created with the correct color value save in line 1.
3.  I have a loadbang set up to send out the color value save to slot one of the UIrecall file. This is where I am running into a problem.  See step 4.
4. I select any one of the four presets and then close and reopen the patcher. The color that was used at the time of saving the patch is loaded rather than the color value in line one of the UIrecall file. 

With each new preset selection the  UIrecall file is cleared, a color value is written into slot one, and the ui preset file is saved.  Like I said this is a hack job, but I'm close.  HELP!

You don't have to save the state to a file, and you don't need to a coll, if you bind it to a pattr object and include a preset object it will store the data in the pattr as a blob and include the data in the patch. I agree it is not intuitive, but if you figure it out it will save you a lot of work. That said, this is my last post on the C74 forums until possibly next year for various reasons including the fact I am mortally ill, so I don't really have the ability to continue being patient with c74 bizzarity at this point. So please don't ask me why it isn't just included in the pattr system in the first place. You could try asking support to fix that, but experience dictates you will be told the same thing I said, you can bind it to a pattr object, and that's the end of that. The actual reason is, pattr was added as a wrapper after the original objects were designed, since when the original designers left and the company doesn't know how to change some of the objects any more. So I told you why anyway before I unsubscribe to all threads. Happy patching and good luck.

Thanks for your help Ernest. I will look into going the pattr route. I would like to not have to create a file for this if I don't have to. Hopefully you're able to stick around the C74 forums, you've been a big help over the years. I understand your frustrations though.

Thanks for your help Ernest. I will look into going the pattr route. I would like to not have to create a file for this if I don't have to.  Hopefully you're able to stick around the C74 forums, you've been a big help over the years. I understand your frustrations though. 

That would be one option.
I think that's what Ernest was saying.

hmmm... I am not seeing how pattr can help me solve this, and that may be due to me being new to the pattr object. Pattr will load last last 

 state of the connected object. In my standalone the Save option is disabled. I am letting the user choose between 4 UI colors. I want the last UI color selected to load on the next relaunch of the standalone. 

. That is why I was looking at the coll oject and having the color values saved to a file.

Help is appreciated and bear with me as I am a total noob to coll and pattr.

hmmm... I am not seeing how pattr can help me solve this, and that may be due to me being new to the pattr object.  Pattr will load last last saved state of the connected object. In my standalone the Save option is disabled. I am letting the user choose between 4 UI colors. I want the last UI color selected to load on the next relaunch of the standalone. No saving involved. That is why I was looking at the coll oject and having the color values saved to a file. 

Help is appreciated and bear with me as I am a total noob to coll and pattr. 

Max.xam, if you want the data to persist after the user closes your patch until the next time they open your patch, you will need to save this data to a file - can be the patch itself (the user would re-save your patch, probably not the best idea), or an external file (usual thing, either saving data in a coll or in a pattr file or even a text file, etc. It's what most commercial software do, saving to a kind of Preferences file).

AFAIK, what you want to achieve is not possible without saving the user preferences to a file.

Max.xam, if you want the data to persist after the user closes your patch until the next time they open your patch, you will need to save this data to a file - can be the patch itself (the user would re-save your patch, probably not the best idea), or an external file (usual thing, either saving data in a coll or in a pattr file or even a text file, etc. It's what most commercial software do, saving to a kind of Preferences file).
AFAIK, what you want to achieve is not possible without saving the user preferences to a file.

Got it! Thanks Jean. I finally got it to work with coll. Woohoo!

How do I auto-load the last swatch color selected after closing and re-opening a patcher?