Nikolas K

Is there something like the "dirty" and "clean" messages to [thispatcher] but for a standalone?

I could add a * next to the title manually but when closing the standalone I will not be prompted to "save changes before closing?".

Is there something like the "dirty" and "clean" messages to [thispatcher] but for a standalone?
I could add a * next to the title manually but when closing the standalone I will not be prompted to "save changes before closing?". 

dirty-and-clean

Well, that is a bit embarrassing... that simple. It works perfectly for me.

I think I answered that a little too quickly...

As it seems, the dialog box flashes (that means it opens) but closes with the patch with no (usable) prompt.

I did a workaround where values changing send a "1" to a [v dirtyState], and the [closebang] checks that state. If 1, it saves with a "name-lastEdit-something" name.

I think I answered that a little too quickly...
As it seems, the dialog box flashes (that means it opens) but closes with the patch with no (usable) prompt.
I did a workaround where values changing send a "1" to a [v dirtyState], and the [closebang] checks that state. If 1, it saves with a "name-lastEdit-something" name. 

but, you actually make user save the *patch* in a built application ???!!!!

Not the patch, just the user's values and params are saved in a file, like presets.

The saving I am referring to is the names of the "presets" saved in that file.

Not the patch, just the user's values and params are saved in a file, like presets.
The saving I am referring to is the names of the "presets" saved in that file.


Are you saving thing with pattrstorage ? because in that case, there's the @savemode attribute which probably would help ?

I am not using pattrstorage, because my interface is dynamic (bpatches are created and removed by the user) and the [pattrstorage] deletes the values that do not exist at the currect state e.g if you have saved 10 numboxes, and then delete some of them, pattrstorage deletes the corresponding values. So its not good for dynamically created interfaces, at least not for me, so I use [dict] to write my values and read them as I like!

Thanks anyway, I think the best options (tried) is a[clasebang] triggering a "save".

Thanks for your time Vichug, I really appreciate it!

I am not using pattrstorage, because my interface is dynamic (bpatches are created and removed by the user) and the [pattrstorage] deletes the values that do not exist at the currect state e.g if you have saved 10 numboxes, and then delete some of them, pattrstorage deletes the corresponding values. So its not good for dynamically created interfaces, at least not for me, so I use [dict] to write my values and read them as I like! 

No problemo ! But a last thing : i remember having a similar patch architecture (bpatchers dynamically created/erased) and using nested pattrstorages (inside bpatchers) to save the presets ; those were ruled by one master pattrstorage (on main patch (let's call it The One to rule them all)). but maybe it didn't work well :D Plus, the whole dict thing might well be an even better, i don't know.

Has anyone found a way to do this?
Thanks in advance. 

Disable any quit key shortcuts and quit messages in standalone,

create button "Quit" which than triggers the whole

because changes made might not be the ones that one really wants to store.

And checking if anything actually changed between last load from

disk and current state should also be implemented if one wanted a real thing.

Disable any quit key shortcuts and quit messages in standalone,
create button "Quit" which than triggers the whole
save or not etc mechanism.
Auto save is in my opinion no go,
because changes made might not be the ones that one really wants to store.
And checking if anything actually changed between last load from
disk and current state should also be implemented if one wanted a real thing.


a somewhat releated issue is that patches in standalones get dirty after scripting. it would be great if patches in standalones would simply never get dirty.

Dirty and Clean