[ESS] TclTk problems with tkentry()/limmaGUI under XEmacs/ESS
Dr Mike Waters
michael.waters at dtn.ntl.com
Tue Nov 30 21:48:10 CET 2004
It seems that you have an incomplete i/o operation there, which is cleared
by the second launch operation.
You can try RamDebugger and its command: Debug->Break
Or you could do what Jeff Hobbs at Activestate suggested to someone with a
similar type problem:
"I would recommend 2 things - better trace output (yes: puts)
during program execution (optionally), or something more like
tkinspect / TDK Inspector. You can see how this app works here:
This will work assuming the "hang" is something stuck at a vwait
or similar problem, not a complete hang of the interpreter. "
> -----Original Message-----
> From: Andreas Quandt [mailto:a.quandt at web.de]
> Sent: 30 November 2004 20:21
> To: Dr Mike Waters
> Subject: RE: [ESS] TclTk problems with tkentry()/limmaGUI
> under XEmacs/ESS
> dear list,
> now I am really confused.
> The earlier posted "solution" by myself is not the solution.
> If I call code from Xemacs/ESS like:
> tt <- tktoplevel()
> txt <- tktext(tt)
> The produced tcl/tk window is hanging after trying to write
> something in the text box. If I call the same code again a
> 2nd window will be created. This 2nd window is full usable.
> After using window 2 the 1st window is also usable and the
> earlier written text there is visible. After a lot of testing
> I have really no ideas any more. All PATH variables are set
> like described ("C:\Tcl\bin", "C:\Tcl\lib\tcl8.4") and
> also the environment variables (TCL_LIBRARY =
> C:\Tcl\lib\tcl8.4, MY_TCLTK = yes).
> So if somebody has any suggestions. Please tell me.
More information about the ESS-help