actually pd-gui was not passing the port number to pd.tk
I didn't spent time figuring out the reason, but I fixed it with commit
10501 [1], by calling 'wish pd.tk' instead of 'pd-gui'
call it a hack, but it worked for me
btw, s_inter.c is very very messy. it's hard to read what it does for
which platform
how about a tidy up? perhaps writing a little cross-platform api for
launching processes (and wish) would allow this...(?)
(but, is the launch order reversed in OSX? i.e. the gui starts the server?)
1:
http://pure-data.svn.sourceforge.net/viewvc/pure-data/branches/pd-devel/0.41...
--
FF
Hans-Christoph Steiner wrote:
> I little self-posting is in order! mescalinum and I have made some
> progress, so I thought I'd document it here.
>
> - on GNU/Linux, pd-gui is a process called pd-gui. On Windows and Mac
> OS X, pd-gui is started using 'wish pd.tk".
>
> - 'pd' starts 'pd.tk' in s_inter.c
>
> - when pd.tk is started by the Wish.app on Mac OS X, pd.tk then starts
> 'pd' using -guiport,
>
> - s_inter.c and t_tkcmd.c are scary
>
> .hc
>
> On Jan 10, 2009, at 11:44 AM, Hans-Christoph Steiner wrote:
>
>
>> One thing that is twisting my brain into knots is the startup order/
>> procedure. It is not very easy to follow and different on each
>> platform. This is something I would really like to smooth out.
>> Right now, I am looking for tips on figuring out everything that is
>> going on. I've searched around some, but am not finding any
>> archived discussions.