Hi all,

Is it possible to use [savepanel] to save a patch .pd file (i.e canvas) instead of File / Save? I already use the [SSSAD] preset saving system provided (which works like a dream to save patch presets) shown below. At the moment I use the [savepanel] to save a txt file of the presets for my patch through SSSAD. So could I also use [savepanel] to then save a pd patch file of the same name I give to the text file for presets or vice versa?

Thanks in advance !

@casper Hello!..... you will need to send the message [savetofile $1 $2( where $1 is the patch file name and $2 is the complete path from root to the folder where you wish to save the file.
That message you send to the patch you want to save so [send pd-thispatch.pd]

There is then another problem to solve. You will see that the patch you are saving is now renamed to its new name, so you need to re-open your patch unless you are happy with the new name........ in which case...... no problem.

You could put this abstraction in your patch (if you want to preserve the file name) .........saveme2.zip but it has to reopen your patch to achieve that, which could be a problem.
David.

thanks for this @whale-av this looks great !. I'll let you know how I go.

Hey @whale-av I've tried your patch and it works great but I would like to try and use [savepanel] to save the pd patch and file name location. So I've tried moding your patch so you can use [savepanel] instead of adding the pathing arguments to it. saveme_newedit.pd But it doesn't seem to work with the savetofile $1.pd $2 message. I've included my patch mod and picture. Any help would be great. Thanks

@casper Your problem is not the [savetofile $1.pd $2( message, but that without the argument the send object below [send pd-$1.pd] has no destination ($1 is not defined).
You can send the message to a canvas by naming it........ so I have put an object [namecanvas woof] and set the message to this patch........ which is then saved. But this is exactly the same as using the menu.... File.... Save as.
saveme_newedit.pd
So that is probably not what you want.
Your abstraction should work if you give it one argument, that is the name of the patch that you want to save (without the extension). But you will end up working in the new saved patch again, as with the patch I have posted above.

I assume that you want to do the same as my original patch, but choose the filename and directory.
I will have to sleep on that and reply later...... time for bed here!

The lack of argument is easily solved by putting the [namecanvas woof] in the patch containing [saveme_newedit] but that is far from a global solution, and you still end up working in the newly saved file.
David.

@casper i think it should be $2 in [send pd-$1.pd] and it has to be the name of the current patch to work.

See also this backup method from an older thread:
savethis.pd

Hi @ingox I tried changing $2 in [send pd-$1.pd] but it didn't work unfortunately.

@whale-av you're right I would like to keep your abstraction but use the [savepanel] to give the user the choice of filename and directory location. I will then include the SSSAD system to produce a text file of the same name to save patch settings etc. Trouble is I'm stuck on how to achieve [savepanel] features in your abstraction. Since my mod still includes the: {symbol $1} {symbol $2] both being packed into the [savetofile $1.pd $2> surely [send pd-$1.pd] should see the filename value stored in {symbol $1} ??
Best

Casper

@casper Sorry, I haven't had time to look at it, and it will be a few days.
No, the two $1 are not the same.
A $1 in a message box takes the value of the first atom in a list that drops into the message on its inlet...... and $2 the second, $3 the third etc.
But the $1 in the [send .....] is in an object box..... not a message box.
$1, $2 etc. in object boxes take the values of the first, second etc. arguments of their patch (usually an abstraction within a "master, or "mother" patch).
So if you put an abstraction [something 3 woof] then within that abstraction every $1 in an object will become 3, and every $2... woof.........
...... but not in a message...
David.

@whale-av no problems at all.

I may have found a solution I found an object called {sendcanvas] which allows you to send up multiple levels of canvas as required. For my work my level happens to be 3. This has saved me naming my parent canvas every time with [namecanvas] now . So it's a global workaround. I'm sure you may come up with something better but here's my patch anyway

@casper That's great. Somewhere in the recycling bin of my very old brain I knew that was possible!..... but I couldn't remember how.....
It's better when you get the solution on your own though. You will not forget......
David.