soundcyst

is there an object that outputs the path of the patch that the object resides in? essentially acting as the unix "pwd" command?

i'm developing an application that i plan to distribute, and i would like the main patch to determine the directory that the set of files is in so that users are not required to put the files in any specific directory.

ideally, the object would output the enclosing directory as a message or symbol in response to a bang, but if there's something close, that's fine too.

i've searched the documentation and dried filepath and such to no avail.

pwd-or-equivalent-object

Quote: the reverend wrote on Fri, 20 February 2009 16:25

----------------------------------------------------

> is there an object that outputs the path of the patch that the object resides in? essentially acting as the unix "pwd" command?

> i'm developing an application that i plan to distribute, and i would like the main patch to determine the directory that the set of files is in so that users are not required to put the files in any specific directory.

> ideally, the object would output the enclosing directory as a message or symbol in response to a bang, but if there's something close, that's fine too.

the thispatcher object will output the path out the right outlet if you send it a "path" message. also there's tons more the thispatcher object can do, it's worth noodling around in the help file, especially the variety of patch window controls available: floating, no menu bar, sizing and position, etc. Not to mention all the scripting possibilities with hide/show, respond to/ignore clicks, moving/resizing objects, etc., essentially most everything you can do to objects in Max as an application, but made available to the end user in a locked patch. very cool.

So that pathname could be used for lots of stuff, including any files your users generate, presets/pattrs/mtr recordings/audio files/video files/etc. they want to save, where it'll auto-save in the same directory and can be auto-reloaded (like in commercial apps where you set a new preset and it appears in the dropdown, and is still there next time you run it, without needing to load it manually). You could also have an option for users to save the given file to a different location.

Note that with paths and/or filenames sometimes you need to be wary of spaces, occasionally this will mess up a command to an object that's expecting a single symbol, and you send it something with a space, no good. Just use tosymbol to convert it.

Quote: the reverend wrote on Fri, 20 February 2009 16:25
----------------------------------------------------
> is there an object that outputs the path of the patch that the object resides in? essentially acting as the unix "pwd" command?
>
> i'm developing an application that i plan to distribute, and i would like the main patch to determine the directory that the set of files is in so that users are not required to put the files in any specific directory.
>
> ideally, the object would output the enclosing directory as a message or symbol in response to a bang, but if there's something close, that's fine too.
>
----------------------------------------------------

Note that with paths and/or filenames sometimes you need to be wary of spaces, occasionally this will mess up a command to an object that's expecting a single symbol, and you send it something with a space, no good. Just use tosymbol to convert it.


> the thispatcher object will output the path out the right outlet if you send it a "path" message. also there's tons more the thispatcher object can do, it's worth noodling around in the help file, especially the variety of patch window controls available: floating, no menu bar, sizing and position, etc. Not to mention all the scripting possibilities with hide/show, respond to/ignore clicks, moving/resizing objects, etc., essentially most everything you can do to objects in Max as an application, but made available to the end user in a locked patch. very cool.

I keep forgetting that lots of these functions have been included in max 5 as attributes: hidden, ignore/respond to click, position (patching rectangle), etc., which is really great as you can use either method to control most things. With thispatcher you need to assign objects a scripting name, but that's easy (and you can have whole arrays of them which can have the same command sent to all). So there's a couple of options for that "next level" of user interactivity, where they can rearrange or resize things, or you could have "basic" and an "advanced" modes: basic = just dials and sliders, advanced = show additional number boxes for finer control, etc. This can get users into the idea without overwhelming them with clutter and options, and then when they start to understand things, open up the additional possibilities. 

> the thispatcher object will output the path out the right outlet if you send it a "path" message. also there's tons more the thispatcher object can do, it's worth noodling around in the help file, especially the variety of patch window controls available: floating, no menu bar, sizing and position, etc. Not to mention all the scripting possibilities with hide/show, respond to/ignore clicks, moving/resizing objects, etc., essentially most everything you can do to objects in Max as an application, but made available to the end user in a locked patch. very cool.
>

I keep forgetting that lots of these functions have been included in max 5 as attributes: hidden, ignore/respond to click, position (patching rectangle), etc., which is really great as you can use either method to control most things. With thispatcher you need to assign objects a scripting name, but that's easy (and you can have whole arrays of them which can have the same command sent to all). So there's a couple of options for that "next level" of user interactivity, where they can rearrange or resize things, or you could have "basic" and an "advanced" modes: basic = just dials and sliders, advanced = show additional number boxes for finer control, etc. This can get users into the idea without overwhelming them with clutter and options, and then when they start to understand things, open up the additional possibilities. 


"pwd" or equivalent object?