pechnatunk

This may have come up before, as it seems like it would be a common frustration.

It would be great if Max/MSP could differentiate between loading a patch and loading a audio file/MIDI file etc. In regard to the folder which opens the next time you open a file.

I keep my mxb, audio and midi files in separate folders and is sometimes a pain to open a mxb file after i've opened an audio file for example. 

I've put shortcuts to common folders inside other common folders but it would be great to not have to do this.

Does anyone else find this a problem or am i just unorganised.

This may have come up  before,  as it seems like it would be a common frustration.

I keep my mxb, audio and midi files in separate folders and is sometimes a pain to open a mxb file after i've opened an audio file for example. 
I've put shortcuts to common folders inside other common folders but it would be great to not have to do this. 

feature-request-open-file-discretion

> I've put shortcuts to common folders inside other common folders but it would be great to not have to do this.

It's not what you're asking for, but a similar feature (also not 

currently implemented) might take care of it indirectly...

Please, please, please: provide a way to specify initial folder location 

to opendialog and savedialog. This would enable all sorts of customized 

behavior that would make life much more bearable for...

> Does anyone else find this a problem or am i just unorganised.

Judging from the way most of the rest of Max's UI seems to work, this 

feature would enable the requested path-defaults for Max itself, too.

pechnatunk wrote:
> I've put shortcuts to common folders inside other common folders but it would be great to not have to do this. 

It's not what you're asking for, but a similar feature (also not 
currently implemented) might take care of it indirectly...

Please, please, please: provide a way to specify initial folder location 
to opendialog and savedialog.  This would enable all sorts of customized 
behavior that would make life much more bearable for...

Judging from the way most of the rest of Max's UI seems to work, this 
feature would enable the requested path-defaults for Max itself, too.

>> I've put shortcuts to common folders inside other common folders but 

>> it would be great to not have to do this.

> It's not what you're asking for, but a similar feature (also not 

> currently implemented) might take care of it indirectly...

> Please, please, please: provide a way to specify initial folder 

> location to opendialog and savedialog. This would enable all sorts of 

> customized behavior that would make life much more bearable for...

I second that request! It would be very useful for me to set the 

default location for all the open dialogs from within Max.

I recently got my hopes up high that this might come earlier: I was 

looking arround for some undocumented messsages to Max and found 

setdlgtofilepath (0/1) and setdialogpath ... I even got something 

written into the maxdialogpath file in the pref directory, but its 

ignored; the paths seem to be stored in the plist. If anyone has any 

further insight how this might work please post ;)

> pechnatunk wrote:
>> I've put shortcuts to common folders inside other common folders but 
>> it would be great to not have to do this.
>
> It's not what you're asking for, but a similar feature (also not 
> currently implemented) might take care of it indirectly...
>
> Please, please, please: provide a way to specify initial folder 
> location to opendialog and savedialog.  This would enable all sorts of 
> customized behavior that would make life much more bearable for...

I second that request! It would be very useful for me to set the 
default location for all the open dialogs from within Max.

I recently got my hopes up high that this might come earlier: I was 
looking arround for some undocumented messsages to Max and found 
setdlgtofilepath (0/1) and setdialogpath ... I even got something 
written into the maxdialogpath file in the pref directory, but its 
ignored; the paths seem to be stored in the plist. If anyone has any 
further insight how this might work please post ;)

> This may have come up before, as it seems like it would be a common frustration.

> It would be great if Max/MSP could differentiate between loading a patch and loading a audio file/MIDI file etc. In regard to the folder which opens the next time you open a file.

> I keep my mxb, audio and midi files in separate folders and is sometimes a pain to open a mxb file after i've opened an audio file for example. 

> I've put shortcuts to common folders inside other common folders but it would be great to not have to do this. 

Oh Vic, you hit the nail on the head right there - in a typical coding 

session I load a number of .pats, and if I need to load a video in any 

of them I have to jump around with shortcuts, when I am ready to load 

the next patches too... All these shortcuts are driving me crazy.

pechnatunk skrev:
> Hi, 
>
> This may have come up  before,  as it seems like it would be a common frustration.
>
> It would be great if Max/MSP could differentiate between loading a patch and loading a audio file/MIDI file etc. In regard to the folder which opens the next time you open a file.
>
> I keep my mxb, audio and midi files in separate folders and is sometimes a pain to open a mxb file after i've opened an audio file for example. 
> I've put shortcuts to common folders inside other common folders but it would be great to not have to do this. 
>
> Does anyone else find this a problem or am i just unorganised.
>
> vic
> ____
Oh Vic, you hit the nail on the head right there - in a typical coding 
session I load a number of .pats, and if I need to load a video in any 
of them I have to jump around with shortcuts, when I am ready to load 
the next patches too... All these shortcuts are driving me crazy.

Feature Request: Open File discretion