Am 20. Mai 2015 04:33:17 MESZ, schrieb William Huston williamahuston@gmail.com:
My understanding is the error either goes to the GUI or to the shell.
I can see the error in the GUI which a pasted into a prior email.
Thus, I see no benefit sending the same error to stderr.
On Tue, May 19, 2015 at 10:21 PM, Pagano, Patrick <pat@digitalworlds.ufl.edu
wrote:
it sends the error to the shell instead of locking up the GUI
*Patrick Pagano B.S, M.F.A* Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020
*From:* William Huston williamahuston@gmail.com *Sent:* Tuesday, May 19, 2015 10:20 PM *To:* Pagano, Patrick *Cc:* rolfmeesters; pd-list@iem.at
*Subject:* Re: [PD] GUI lock ups
Thanks Patrick. Can you explain how this will help?
I'm using Windows 7, so there is normally no parent shell.
So -stderr flag (if I am understanding correctly) would take the
errors
which I can presently see in the GUI console, and send them to the
"bit
bucket" (invisible to me).
I can start pd -stderr from a shell, no problem, if there is some
benefit.
Do you think there will be additional diagnostics generated above
what I
have already provided?
Thanks,
On Tuesday, May 19, 2015, Pagano, Patrick pat@digitalworlds.ufl.edu wrote:
add the -stderr flag to your boot
Patrick Pagano B.S, M.F.A Audio and Projection Design Faculty Digital Worlds Institute University of Florida, USA (352)294-2020 ________________________________ From: Pd-list pd-list-bounces@mail.iem.at on behalf of William
Huston
Sent: Tuesday, May 19, 2015 9:29 PM To: rolfmeesters Cc: pd-list@iem.at Subject: Re: [PD] GUI lock ups
Yes, just happened:
(Tcl) INVALID COMMAND NAME: invalid command name ".x3cc9380.c" while executing "$tkcanvas itemconfig $tag -text $text" (procedure "pdtk_text_set" line 2) invoked from within "pdtk_text_set .x3cc9380.c .x3cc9380.t43bfcc0 {4.326}" ("uplevel" body line 1) invoked from within "uplevel #0 $cmds_from_pd"
0.43.4-extended, Windows 7
Thanks
On Mon, May 18, 2015 at 3:16 PM, William Huston <
williamahuston@gmail.com> wrote:
Hmm. Not sure. Will check console next time it happens. Thanks.
On Mon, May 18, 2015 at 5:52 AM, rolfm@dds.nl wrote:
do you also get TCL errors ?
rolf
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
--
May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)
Don't forget to sign the Pledge to Resist the Constitution Pipeline:
The Pledge: TinyURL.com/Pledge2ResistCP More info: TinyURL.com/Pledge2ResistCP1
--
May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)
Don't forget to sign the Pledge to Resist the Constitution Pipeline:
The Pledge: TinyURL.com/Pledge2ResistCP More info: TinyURL.com/Pledge2ResistCP1
--
May you, and all beings be happy and free from suffering :) -- ancient Buddhist Prayer (Metta)
Don't forget to sign the
*Pledge to Resist *
*the Constitution Pipeline: *
- *The Pledge: TinyURL.com/Pledge2ResistCP
http://TinyURL.com/Pledge2ResistCP*
- *More info: TinyURL.com/Pledge2ResistCP1
Hi,
sending the messages to the command line will prevent them from being interpreted as Tcl commands, which most probably is the cause for your error.
cu Thomas
Sent from a mobile device.