just to inform you of the existence of this hack of mine. The attachment mentioned below is downloadable at:
http://artengine.ca/jmax/gridflow/gallery/pd_console.diff
---------- Forwarded message ---------- Date: Sun, 25 Jan 2004 04:24:52 -0500 (EST) From: Mathieu Bouchard matju@sympatico.ca To: pd-dev@iem.kug.ac.at Subject: Pd Console
The attachment on this file is the output of "cvs diff -u" containing my modifications to Pd such that you can do this:
pd -console 500
where 500 is the number of scrollback lines you want; this creates a Tk text widget to which post() and [print] are redirected. This is most helpful when you don't have a terminal to launch Pd from, but it's also helpful if you like to have one window less.
I submit this for inclusion into the main Pd branch.
screenshot:
http://artengine.ca/jmax/gridflow/gallery/pd_console.gif
Any suggestions?
Mathieu Bouchard http://artengine.ca/matju
I've been planning to do this for years... so probably I'll put this into pd 0.38 (once I finish dealing with all the bugs in 0.37... maybe that will never happen...)
One complication: in 0.38 I want to make scheduled graphics updates so that even extremely graphics-heavy patches run without dac underruns. The GUI post() will have to be fixed to deal with flow control somehow.
cheers Miller
On Sun, Jan 25, 2004 at 07:47:53PM -0500, Mathieu Bouchard wrote:
just to inform you of the existence of this hack of mine. The attachment mentioned below is downloadable at:
http://artengine.ca/jmax/gridflow/gallery/pd_console.diff
---------- Forwarded message ---------- Date: Sun, 25 Jan 2004 04:24:52 -0500 (EST) From: Mathieu Bouchard matju@sympatico.ca To: pd-dev@iem.kug.ac.at Subject: Pd Console
The attachment on this file is the output of "cvs diff -u" containing my modifications to Pd such that you can do this:
pd -console 500
where 500 is the number of scrollback lines you want; this creates a Tk text widget to which post() and [print] are redirected. This is most helpful when you don't have a terminal to launch Pd from, but it's also helpful if you like to have one window less.
I submit this for inclusion into the main Pd branch.
screenshot:
http://artengine.ca/jmax/gridflow/gallery/pd_console.gif
Any suggestions?
Mathieu Bouchard http://artengine.ca/matju
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Sun, 25 Jan 2004, Miller Puckette wrote:
I've been planning to do this for years...
I've been working on this for hours...
Besides I also plan a lot of things that still don't happen after a few years. Look at my TODO list =)
so probably I'll put this into pd 0.38 (once I finish dealing with all the bugs in 0.37... maybe that will never happen...)
Well, the way I have designed the patch, it is OFF by default, and it should be fairly easy to check that unless you write "-console" on Pd's commandline, it doesn't do anything, so even though it's an experimental feature, it's nonintrusive, and should be appliable right now safely.
[note: If this were a nonoptional feature, I would have recommended waiting]
Btw, jMax has had that for many years... and it's an optional feature too (Though ON by default).
One complication: in 0.38 I want to make scheduled graphics updates so that even extremely graphics-heavy patches run without dac underruns.
The GUI post() will have to be fixed to deal with flow control somehow.
Have you read my mail about sys_gui()? what do you think of that?
Mathieu Bouchard http://artengine.ca/matju
Hi Mathieu, a while ago i announced and introduced a modification to the devel_0_37 branch which implements the ability to hook the console output - it's a mechanism that allows multiple listeners (via callbacks) to eavesdrop on the printouts. Is there any specific reason why you didn't take on this patch? Your widget could easily use it, while leaving open other forms of console output.
The respective API functions of devel_0_37 are sys_addprinthook and sys_rmprinthook.
best greetings, Thomas
----- Original Message ----- From: "Mathieu Bouchard" matju@sympatico.ca To: pd-list@iem.kug.ac.at Sent: Monday, January 26, 2004 1:47 AM Subject: [PD] Pd Console (fwd)
just to inform you of the existence of this hack of mine. The attachment mentioned below is downloadable at:
http://artengine.ca/jmax/gridflow/gallery/pd_console.diff
---------- Forwarded message ---------- Date: Sun, 25 Jan 2004 04:24:52 -0500 (EST) From: Mathieu Bouchard matju@sympatico.ca To: pd-dev@iem.kug.ac.at Subject: Pd Console
The attachment on this file is the output of "cvs diff -u" containing my modifications to Pd such that you can do this:
pd -console 500
where 500 is the number of scrollback lines you want; this creates a Tk text widget to which post() and [print] are redirected. This is most helpful when you don't have a terminal to launch Pd from, but it's also helpful if you like to have one window less.
I submit this for inclusion into the main Pd branch.
screenshot:
http://artengine.ca/jmax/gridflow/gallery/pd_console.gif
Any suggestions?
Mathieu Bouchard http://artengine.ca/matju
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Thu, 29 Jan 2004, Thomas Grill wrote:
a while ago i announced and introduced a modification to the devel_0_37 branch which implements the ability to hook the console output - it's a mechanism that allows multiple listeners (via callbacks) to eavesdrop on the printouts. Is there any specific reason why you didn't take on this patch? Your widget could easily use it, while leaving open other forms of console output. The respective API functions of devel_0_37 are sys_addprinthook and sys_rmprinthook.
Good question. The reason is that enough messages get posted around here that I often delete many quite quickly, and sometimes I miss something interesting, thinking it's not.
Besides, I don't use devel_0_37, because I don't know what are the several branches of Pd, how they relate to each other, what are the differences, and which one I should use.
If your patch is complete, then it would be a good idea to use it in a future version of mine, as there are many stderr messages I don't actually handle at all. I think many/most error messages still get sent to stderr...
Mathieu Bouchard http://artengine.ca/matju
Besides, I don't use devel_0_37, because I don't know what are the several branches of Pd, how they relate to each other, what are the differences, and which one I should use.
devel_0_37 is the experimental branch of pd 0.37. It seems to be quite common that patches for pd 0.37 are introduced there. To my knowledge there are no other commonly used cvs branches.
If your patch is complete, then it would be a good idea to use it in a future version of mine, as there are many stderr messages I don't actually handle at all. I think many/most error messages still get sent to stderr...
Naturally, my modification redirects only the printout functions declared in s_print.c, but can't capture those directly printed to stdout or stderr.
best greetings, Thomas
There's a trick here which is figuring out how to deal with errors that might mean the GUI can't start up at all or will soon die... and yet other messages which come up before the GUI has been started (does one store them and send them all up once the GUI is alive?) hmm....
Miller
On Thu, Jan 29, 2004 at 07:11:48PM +0100, Thomas Grill wrote:
Besides, I don't use devel_0_37, because I don't know what are the several branches of Pd, how they relate to each other, what are the differences, and which one I should use.
devel_0_37 is the experimental branch of pd 0.37. It seems to be quite common that patches for pd 0.37 are introduced there. To my knowledge there are no other commonly used cvs branches.
If your patch is complete, then it would be a good idea to use it in a future version of mine, as there are many stderr messages I don't actually handle at all. I think many/most error messages still get sent to stderr...
Naturally, my modification redirects only the printout functions declared in s_print.c, but can't capture those directly printed to stdout or stderr.
best greetings, Thomas
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
Tigital's idea of outputing the messages to the system's 'console'
could help in that regard, though its currently implemented for MacOS
X, it should be an easy UNIX port using syslog. The Windows EventLog
might be a bit more complicated.
.hc
On Thursday, Jan 29, 2004, at 13:35 America/New_York, Miller Puckette
wrote:
There's a trick here which is figuring out how to deal with errors
that might mean the GUI can't start up at all or will soon die... and yet other messages which come up before the GUI has been started (does one store
them and send them all up once the GUI is alive?) hmm....Miller
On Thu, Jan 29, 2004 at 07:11:48PM +0100, Thomas Grill wrote:
Besides, I don't use devel_0_37, because I don't know what are the
several branches of Pd, how they relate to each other, what are the
differences, and which one I should use.devel_0_37 is the experimental branch of pd 0.37. It seems to be quite common that patches for pd 0.37 are introduced there. To my knowledge there are no other commonly used cvs branches.
If your patch is complete, then it would be a good idea to use it in
a future version of mine, as there are many stderr messages I don't
actually handle at all. I think many/most error messages still get sent to stderr...Naturally, my modification redirects only the printout functions
declared in s_print.c, but can't capture those directly printed to stdout or
stderr.best greetings, Thomas
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
"Information wants to be free." -Stewart Brand
On Thu, 29 Jan 2004, Thomas Grill wrote:
devel_0_37 is the experimental branch of pd 0.37. It seems to be quite common that patches for pd 0.37 are introduced there. To my knowledge there are no other commonly used cvs branches.
Okay, I attached a diff that is a new version of my console, with the following changes:
Tell me what you think of it.
Mathieu Bouchard http://artengine.ca/matju