P_Petrowiek

i'm having a weird problem with coll that i've never had : 

I use a powerbook G4 running MacOS10.3.9.

Now, in my patch, i use a message "sprintf write %i_leSeq" that i send to coll where %i is the variable for the name of my coll...

The problem is that my coll is saved in the Max4.6 folder (in application) when it would normally be supposed to be saved in the folder where the patch is located !

I don't want to use a message like "sprintf write (and here a certain path)" as i want coll to be saved automatically where the patch in which coll is included is located...

Gosh, my english is a little weird and i hope you guys will understand me.

Hi,
i'm having a weird problem with coll that i've never had : 
I use a powerbook G4 running MacOS10.3.9.
Max is 4.6.2 and Jitter is 1.6.2

Now, in my patch, i use a message "sprintf write %i_leSeq" that i send to coll where %i is the variable for the name of my coll...
ex : 1_leSeq.
The problem is that my coll is saved in the Max4.6 folder (in application) when it would normally be supposed to be saved in the folder where the patch is located !

Am i wrong or what ?
Why is coll saved in the Max4.6 folder ?
I don't want to use a message like "sprintf write (and here a certain path)" as i want coll to be saved automatically where the patch in which coll is included is located...

write-with-coll

Me again just to say that i tried with a message "sprintf write %i_leSeq ./" and it kinda works but this solution has two major problems : 

- It's not cross platform as on a pc it would be .

- it pushes Max to send a warning message saying "extra argument for message write" (and it's not clean... i don't like that kind of things.

Me again just to say that i tried with a message "sprintf write %i_leSeq ./" and it kinda works but this solution has two major problems : 
- It's not cross platform as on a pc it would be .
- it pushes Max to send a warning message saying "extra argument for message write" (and it's not clean... i don't like that kind of things.

On 26 oct. 06, at 10:40, tworowski.sebastien wrote:

> Now, in my patch, i use a message "sprintf write %i_leSeq" that i 

> send to coll where %i is the variable for the name of my coll...

> The problem is that my coll is saved in the Max4.6 folder (in 

> application) when it would normally be supposed to be saved in the 

Essaie quelque-chose comme ceci (il faut d'abord sauvegarder le patch):

On 26 oct. 06, at 10:40, tworowski.sebastien wrote:
> Now, in my patch, i use a message "sprintf write %i_leSeq" that i  
> send to coll where %i is the variable for the name of my coll...
> ex : 1_leSeq.
> The problem is that my coll is saved in the Max4.6 folder (in  
> application) when it would normally be supposed to be saved in the  
> folder where the patch is located !

Nice try but it didn't help as my problem is different now...

But as i don't really understand my problem for the moment, it's impossible to explain it :P

Nice try but it didn't help as my problem is different now...
But as i don't really understand my problem for the moment, it's impossible to explain it :P

try prepending the write argument with the output of sending path to thispatcher if all else fails.

alternatively use filepath in default mode.

this will set your new path location explicitly.

this way, all you have to do is utilize opendialog or whatnot and choose the location once.

you can bang this location upon loading your patch...

alternatively use filepath in default mode.
this will set your new path location explicitly.
this way, all you have to do is utilize opendialog or whatnot and choose the location once.
you can bang this location upon loading your patch...

> Me again just to say that i tried with a message "sprintf write

> %i_leSeq ./" and it kinda works but this solution has two major

> problems : - It's not cross platform as on a pc it woulb . - it

> pushes Max to send a warning message saying "extra argument for

> message write" (and it's not clean... i don't like that kind of

There is a problem with the subject. I have no idea what you are 

reffering to. It sounds as it belongs to an existing thread...???

If you get a warning "extra argument for message write" It means there 

are more arguments than write is supposed to have. If it kinda works, it 

will work crossplatform, because the part which you think is platform 

specific is ignored, and thus will be ignored on both platforms...

The clean solution would be to do just "sprintf write %i_leSeq" which 

tworowski.sebastien wrote:
> Me again just to say that i tried with a message "sprintf write
> %i_leSeq ./" and it kinda works but this solution has two major
> problems : - It's not cross platform as on a pc it woulb . - it
> pushes Max to send a warning message saying "extra argument for
> message write" (and it's not clean... i don't like that kind of
> things.
>
> Any clean solution ? Thanks 

There is a problem with the subject. I have no idea what you are 
reffering to. It sounds as it belongs to an existing thread...???
There is no quote either to find out...

If you get a warning "extra argument for message write" It means there 
are more arguments than write is supposed to have. If it kinda works, it 
will work crossplatform, because the part which you think is platform 
specific is ignored, and thus will be ignored on both platforms...

The clean solution would be to do just "sprintf write %i_leSeq" which 
seems to "kinda work"...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


write with coll