Guillaume Evrard

i'm facing a strange behavior from pcontrol. when i load a patcher by sending the "load [mypatcher]" message, every #x in [mypatcher] is replaced by '0'(if x>0), and every #0 is replaced by a pid number. As [mypatcher] is editable, #0 should be '#0' and #x should be '#x' ... weird.

loading-a-patch-with-pcontrol

> i'm facing a strange behavior from pcontrol. when i load a patcher by

> sending the "load [mypatch]" message, every #x in [mypatcher] is

> replaced by '0'(if x>0), and every #0 is replaced by a pid number. As

> [mypatcher] is editable, #0 should be '#0' and #x should be '#x' ...

Yes it seems to be a bug, or feature, dependent on the context. You must 

not save a patch opened like that, elsewise you destroy the original.

It might make sense though, as you usually won't open patches which 

require arguments with pcontrol, and that way they would have at least a 

But I agree, I vote for being it a bug, as its pontentially dangerous, 

and of no specific use. As there was no answer to that post, I'd wonder 

This bug might be related to another observation I made, where for no 

reason I was aware of, suddenly #0 arguments showed up in my patches as 

former unique numbers, rendering multiple instances of the patcher non 

functioning. I don't know how this happend, but might be related to that...

guillaume schrieb:
> i'm facing a strange behavior from pcontrol. when i load a patcher by
> sending the "load [mypatch]" message, every #x in [mypatcher] is
> replaced by '0'(if x>0), and every #0 is replaced by a pid number. As
> [mypatcher] is editable, #0 should be '#0' and #x should be '#x' ...
> weird.

Yes it seems to be a bug, or feature, dependent on the context. You must 
not save a patch opened like that, elsewise you destroy the original.
It might make sense though, as you usually won't open patches which 
require arguments with pcontrol, and that way they would have at least a 
meaningless value passed...

But I agree, I vote for being it a bug, as its pontentially dangerous, 
and of no specific use. As there was no answer to that post, I'd wonder 
if it was recognized by cycling...

This bug might be related to another observation I made, where for no 
reason I was aware of, suddenly #0 arguments showed up in my patches as 
former unique numbers, rendering multiple instances of the patcher non 
functioning. I don't know how this happend, but might be related to that...

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

thanks for your reply, i also vote for this to be a bug.

my goal was to have a nice button "new project" in my application, wich load the template i made. my projects need #0 and #1 to be identified in the plateform i made. So i can't make my nice "new project" button.

i tried to identified the pid (the one wich replace my #0 when loadind with pcontrol) but i can't manage to find this process, maybe it's the "open" routine of the max system.

the question is : what's the difference between file->open and load->pcontrol.

i think this two way to open a patch should act similarly (in a perfect world).

anyway, max 5 is coming, with no weird behaviors or bugs of course :)

thanks for your reply, i also vote for this to be a bug.
my goal was to have a nice button "new project" in my application, wich load the template i made. my projects need #0 and #1 to be identified in the plateform i made. So i can't make my nice "new project" button.

> the question is : what's the difference between file->open and

You could try to open the patch with the launchbrowser message to Max, 

then the OS is opening it and not Max. I'd give it a try...

guillaume schrieb:
> the question is : what's the difference between file->open and
> load->pcontrol.

You could try to open the patch with the launchbrowser message to Max, 
then the OS is opening it and not Max. I'd give it a try...

[; max launchbrowser file:///Volumes/Data/path/to/the/file.mxt]

wow, nice trick.
[; max launchbrowser file:///Volumes/Data/path/to/the/file.mxt]
i think it just works fine.
thanks a lot.
g


for your information, this way to open a patch allow you to launch any application from Max. When the path point to a file, this file is opened with the default application, specified in your OS preferences.

Holy cow! I had always thought the launchbrowser meant Max opened a Web browser only, and you could only go to a URL. But you can drop any file and it opens with the default application.... that is really great! Not mentioned in the docs, at least that I found --- that would be good to include in there.

Guess I just never thought of it. But when you said

"You could try to open the patch with the launchbrowser message to Max, then the OS is opening it and not Max."

it got me thinking. Great stuff, thanks ! !

Holy cow!  I had always thought the launchbrowser meant Max opened a Web browser only, and you could only go to a URL. But you can drop any file and it opens with the default application.... that is really great!  Not mentioned in the docs, at least that I found --- that would be good to include in there. 

loading a patch with pcontrol