This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: can't run xconq due to BWidget
- From: Hans Ronne <hronne at pp dot sbbs dot se>
- To: MA Dunzi <tadalunch at s5 dot xrea dot com>
- Cc: xconq7 at sources dot redhat dot com
- Date: Tue, 8 Oct 2002 23:22:10 +0200
- Subject: Re: can't run xconq due to BWidget
- References: Your message of "Mon, 7 Oct 2002 14:38:03 -0400 (EDT)".<200210071838.g97Ic3K05158@panix1.panix.com>
> | although that didn't seem to work for me (and I don't know how to get
> | real error messages out of tcl rather than the "error reading tcl"
> | thing).
>
>set tcl_traceCompile 1
>set tcl_traceExec 1
>
>these variables might be helpful to you.
Not sure what this discussion is all about since the original message was
not posted to the xconq7 list, but anyway, there is also some built-in
debugging in tkconq.tcl. Just change:
set debug 0
to:
set debug 1
Not that it helps a lot. Debugging tcl scripts is not for the faint of
heart :-). What I really hate is not the bogus "error reading tcl" error
message but rather all the times tcl silently fails to do something because
of a typo. If you don't get an error message, how can you tell that
something went wrong?
Hans
Hans Ronne
hronne@pp.sbbs.se