saving patches always brings up file dialog

You should be able to use cmd+S, maybe your permissions are set to prevent
you overwriting the files? You can check this by selecting a file and
choosing get info. (I've never used 10.5 though stil on 10.4)

pelado

> i'm just starting to use Max5 and it would seem (10.5 MacBook Pro, Max
> 5.0.5) that I can't save (overwrite) patches using Command + S or the file
> menu without Max poppin' up the 'ol file menu.
>
> what gives? anyone else seen this?
>
>

or you've got a character in it that's making it difficult, like a
slash.

On Jan 18, 2009, at 4:06 PM, pelado wrote:

> You should be able to use cmd+S, maybe your permissions are set to
> prevent you overwriting the files? You can check this by selecting
> a file and choosing get info. (I've never used 10.5 though stil on
> 10.4)
>
> pelado
>
>
> i'm just starting to use Max5 and it would seem (10.5 MacBook Pro,
> Max 5.0.5) that I can't save (overwrite) patches using Command + S
> or the file menu without Max poppin' up the 'ol file menu.
>
> what gives? anyone else seen this?
>
>

On 18 Jan 2009, at 21:06, pelado wrote:

> You should be able to use cmd+S, maybe your permissions are set to
> prevent you overwriting the files? You can check this by selecting
> a file and choosing get info. (I've never used 10.5 though stil on
> 10.4)

As I recall, Max5 will prompt to save its new-format (.maxpat) files
if you've opened old Max4-format ones.

    -- N.

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.reverbnation.com/cassiel
www.linkedin.com/in/cassiel
www.loadbang.net

On 18 janv. 09, at 22:49, Nick Rothwell wrote:

>> You should be able to use cmd+S, maybe your permissions are set to
>> prevent you overwriting the files? You can check this by selecting
>> a file and choosing get info. (I've never used 10.5 though stil on
>> 10.4)
>
> As I recall, Max5 will prompt to save its new-format (.maxpat) files
> if you've opened old Max4-format ones.

That's correct, but once it's a maxpat, it shouldn't bring the save
dialog box unless there's some permissions issues.

Best,
ej

bah - there WAS a slash way up a few levels that i didn't see - cheers y'all!

I've been having the same issue and it was driving me crazy. Sometimes it just saved, and sometimes I would have to overwrite it. I think this would happen whenever saving the patch outside of the max search path because now its fine.

Andrew

Another thing that can happen is if your patch is sending a 'patcher ' message to thispatcher. The name change causes Save to bring up the Save As… dialog to confirm the new name.

I find this scenario usually easier to track down than permissions issues, but it can also be a gotcha.

I'm having the exact same problem, but in my case, it seems to be dependent on which of my two computers I'm using. If I create a new patcher and just put a single message box in it and save it with the name test.maxpat, I am initially prompted--as expected--to give the file a name. BUT, if I reopen that file on my Desktop computer (G4, OS 10.4.11) and make any change to the file and choose save (cmd-s), I am prompted to give the file a name and if I use the same name am told that there is an older file with the same name...

If I do the exact same thing on my laptop (Intel Core 2 Duo, OS 10.5.6) it works just fine--no prompt to name the file, etc.

BTW, I checked permissions and they are set to read & write, and the patch is so simple that the problems like thispatcher don't apply for me. I just always get prompted with a file dialog whenever I choose "Save" (cmd-s) on my G4 and I don't on my Intel PowerBook.