Fix occassional exceptions on tcl/tk 8.6 when executing python scripts from the GUI.
From: santiago
This commit is contained in:
parent
31dfc0ccf2
commit
aa3023ae62
1 changed files with 7 additions and 0 deletions
|
@ -1076,6 +1076,13 @@ proc parseRegMessage { data len flags channel } {
|
||||||
# reg message with session number indicates the sid of a session that
|
# reg message with session number indicates the sid of a session that
|
||||||
# was just started from XML or Python script (via reg exec=scriptfile.py)
|
# was just started from XML or Python script (via reg exec=scriptfile.py)
|
||||||
if { $session != "" } {
|
if { $session != "" } {
|
||||||
|
# The channel passed to here is soon after discarded for
|
||||||
|
# sessions that are started from XML or Python scripts. This causes
|
||||||
|
# an exception in the GUI when responding back to daemon if the
|
||||||
|
# response is sent after the channel has been destroyed. Setting
|
||||||
|
# the channel to -1 basically disables the GUI response to the daemon,
|
||||||
|
# but it turns out the daemon does not need the response anyway.
|
||||||
|
set channel -1
|
||||||
# assume session string only contains one session number
|
# assume session string only contains one session number
|
||||||
connectShutdownSession connect $channel $session $fnhint
|
connectShutdownSession connect $channel $session $fnhint
|
||||||
return
|
return
|
||||||
|
|
Loading…
Reference in a new issue