wasm-demo/demo/ermis-f/python_m/cur/0117

51 lines
1.8 KiB
Plaintext

From: duncan at rcp.co.uk (Duncan Booth)
Date: 15 Apr 1999 08:58:10 GMT
Subject: 1.5.2 install problems on NT
References: <3714D8FF.634655C5@ina.fr>
Message-ID: <8DA968455duncanrcpcouk@news.rmplc.co.uk>
Content-Length: 1555
X-UID: 117
Richard GRUET <rgruet at ina.fr> wrote in <3714D8FF.634655C5 at ina.fr>:
>cl problems:
>---------------
>shared by many ! see Hoon Yoon for instance... wish80;exe works (hence I
>conclude that tcl is installed properly) but IDLE or Tkdb don't, with
>insults like:
>C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl: bad event type
>bad event type or keysym "MouseWheel"
> while executing
>"bind Listbox <MouseWheel> {
> %W yview scroll [expr - (%D / 120) * 4] units
>}"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/listbox.tcl
> invoked from within
>"source [file join $tk_library listbox.tcl]"
> (file "C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl" lin
> invoked from within
>"source C:/PROGRA~1/PYTHON/TCL/lib/tk8.0/tk.tcl"
> ("uplevel" body line 1)
> invoked from within
>"uplevel #0 [list source $tkfile]"
>
>This probably means that Tk wasn't installed properly.
>
I had exactly that problem. I think it means that you upgraded an old Tcl
system but there are still copies of the old Tcl80.dll files lying around
somewhere and python is finding those in preference to the new ones.
Delete tcl80.dll from the \winnt\system32 directory or wherever they
are, and add the tcl bin directory (e.g. D:\Progra~1\Tcl\Bin) to the end of
your path in the control manager/system/environment settings.
--
Duncan Booth duncan at dales.rmplc.co.uk
int month(char *p){return(124864/((p[0]+p[1]-p[2]&0x1f)+1)%12)["\5\x8\3"
"\6\7\xb\1\x9\xa\2\0\4"];} // Who said my code was obscure?
http://dales.rmplc.co.uk/Duncan