Martin Peach <martin.peach <at> sympatico.ca> writes:
Martin Peach wrote:
can't read "box_outline": no such variable can't read "msg_nlet": no such variable can't read "msg_nlet": no such variable can't read "msg_nlet": no such variable can't read "text_color": no such variable can't read "cursor_runmode_nothing": no such variableI checked it on linux and it seems the only difference between the windows and linux versions is that the variables that are set in
pd.tk
and referenced from pd via sys_vgui() aren't being found, so nothing gets drawn on the canvas.
Martin
Ok, got a bit closer on this one, finally. It seems that all of the
code is the same up thru tcl_mess() in t_tkcmd.c. Once the tcl data
from sys_vgui() is sent to the tcl process and chopped up into
distinct commands, tcl_mess() is used to send the command to the Tcl
process ("tk_pdinterp" is the tcl process, "s" is the command):
result = Tcl_Eval(tk_pdinterp, s);
I tried to print out "s" here, but I couldn't get it to show up. It
seems that stderr is a bit strange on Windows. My hunch is that
something on Windows is eating the "$", and therefore causing this
problem.
Anyone know a way to get this to show up on the Windows console:
fprintf(stderr, "tcl_mess: %s\n", ms);
.hc
News is what people want to keep hidden and everything else is
publicity. - Bill Moyers
Hans-Christoph Steiner wrote:
Ok, got a bit closer on this one, finally. It seems that all of the
code is the same up thru tcl_mess() in t_tkcmd.c. Once the tcl data
from sys_vgui() is sent to the tcl process and chopped up into
distinct commands, tcl_mess() is used to send the command to the Tcl
process ("tk_pdinterp" is the tcl process, "s" is the command):result = Tcl_Eval(tk_pdinterp, s);I tried to print out "s" here, but I couldn't get it to show up. It
seems that stderr is a bit strange on Windows. My hunch is that
something on Windows is eating the "$", and therefore causing this
problem.Anyone know a way to get this to show up on the Windows console:
fprintf(stderr, "tcl_mess: %s\n", ms);
Try running pd from a .bat file. Or fprint(stdout... instead.
Martin
On Feb 24, 2008, at 11:36 PM, Martin Peach wrote:
Hans-Christoph Steiner wrote:
Ok, got a bit closer on this one, finally. It seems that all of
the code is the same up thru tcl_mess() in t_tkcmd.c. Once the
tcl data from sys_vgui() is sent to the tcl process and chopped
up into distinct commands, tcl_mess() is used to send the command
to the Tcl process ("tk_pdinterp" is the tcl process, "s" is the
command): result = Tcl_Eval(tk_pdinterp, s); I tried to print out "s" here, but I couldn't get it to show up.
It seems that stderr is a bit strange on Windows. My hunch is
that something on Windows is eating the "$", and therefore
causing this problem. Anyone know a way to get this to show up on the Windows console: fprintf(stderr, "tcl_mess: %s\n", ms);Try running pd from a .bat file. Or fprint(stdout... instead.
Using fprint(stdout... in the msys bash shell worked. It did not
work in the CMD.EXE shell window, nothing shows up. Plus fprint
(stderr... doesn't seem to work anywhere. Arg, Windows is a pain...
So now, printing out the Tcl commands shows the "$" in "$text_color",
etc. intact, so I guess it's dropping it in Tcl-space... on that
note, I'm going to bed. Any ideas?
.hc
Man has survived hitherto because he was too ignorant to know how to
realize his wishes. Now that he can realize them, he must either
change them, or perish. -William Carlos Williams
Hans-Christoph Steiner wrote:
On Feb 24, 2008, at 11:36 PM, Martin Peach wrote:
Hans-Christoph Steiner wrote:
Ok, got a bit closer on this one, finally. It seems that all of the
code is the same up thru tcl_mess() in t_tkcmd.c. Once the tcl data
from sys_vgui() is sent to the tcl process and chopped up into
distinct commands, tcl_mess() is used to send the command to the Tcl
process ("tk_pdinterp" is the tcl process, "s" is the command): result = Tcl_Eval(tk_pdinterp, s); I tried to print out "s" here, but I couldn't get it to show up. It
seems that stderr is a bit strange on Windows. My hunch is that
something on Windows is eating the "$", and therefore causing this
problem. Anyone know a way to get this to show up on the Windows console: fprintf(stderr, "tcl_mess: %s\n", ms);Try running pd from a .bat file. Or fprint(stdout... instead.
Using fprint(stdout... in the msys bash shell worked. It did not work in the CMD.EXE shell window, nothing shows up. Plus fprint(stderr... doesn't seem to work anywhere. Arg, Windows is a pain...
Windows tcl is a pain because it's not quite the same as unix tcl.
So now, printing out the Tcl commands shows the "$" in "$text_color", etc. intact, so I guess it's dropping it in Tcl-space... on that note, I'm going to bed. Any ideas?
What it seemed like to me was that tcl thinks it's a different address space so the variables defined in pd.tk are not recognized. If you could get both ends to print out the name of their address space it might help.
Martin
On Feb 25, 2008, at 9:18 AM, Martin Peach wrote:
Hans-Christoph Steiner wrote:
On Feb 24, 2008, at 11:36 PM, Martin Peach wrote:
Hans-Christoph Steiner wrote:
Ok, got a bit closer on this one, finally. It seems that all of
the code is the same up thru tcl_mess() in t_tkcmd.c. Once the
tcl data from sys_vgui() is sent to the tcl process and chopped
up into distinct commands, tcl_mess() is used to send the
command to the Tcl process ("tk_pdinterp" is the tcl process,
"s" is the command): result = Tcl_Eval(tk_pdinterp, s); I tried to print out "s" here, but I couldn't get it to show
up. It seems that stderr is a bit strange on Windows. My
hunch is that something on Windows is eating the "$", and
therefore causing this problem. Anyone know a way to get this to show up on the Windows console: fprintf(stderr, "tcl_mess: %s\n", ms);Try running pd from a .bat file. Or fprint(stdout... instead.
Using fprint(stdout... in the msys bash shell worked. It did not
work in the CMD.EXE shell window, nothing shows up. Plus fprint (stderr... doesn't seem to work anywhere. Arg, Windows is a pain...Windows tcl is a pain because it's not quite the same as unix tcl.
So now, printing out the Tcl commands shows the "$" in
"$text_color", etc. intact, so I guess it's dropping it in Tcl- space... on that note, I'm going to bed. Any ideas?What it seemed like to me was that tcl thinks it's a different
address space so the variables defined in pd.tk are not recognized.
If you could get both ends to print out the name of their address
space it might help.
I am off to LAC so I won't have time to look at this for at least a
week. If anyone can take a stab, I'd greatly appreciate it. I'll
try again after I am back in New York in the middle of next week.
.hc
'You people have such restrictive dress for women,’ she said,
hobbling away in three inch heels and panty hose to finish out
another pink-collar temp pool day. - “Hijab Scene #2", by Mohja Kahf
-
Hans-Christoph Steiner -
Martin Peach