Alexander Kurpiers <[EMAIL PROTECTED]> writes:
--------
Dear Ptolemy Hackers!
I want to track down the annoying bug in KDE that keeps Ptolemy Classic
from being usable under that environment. The problem is that if a
window pops up using ptkImportantMessage() this window needs 30 seconds
to go away. This is probably a bug in KDE (actually in kpanel > 1.0 but
even KDE 2.x which does not have kpanel anymore has this bug).
I want to isolate the Tcl function that implements ptkImportantMessage
but could not find it in the source code. Where do I have to look? The
idea is to have a small piece of code that runs without ptolemy to find
the bug in KDE.
Thanks!
Alexander
--
Alexander F. Kurpiers | Voice: +49-6151-162369
Institut fuer Nachrichtentechnik | Fax : +49-6151-165545
Merckstrasse 25 | EMail: [EMAIL PROTECTED]
D-64283 Darmstadt (Germany) | Hamradio: dl8aau@db0ais.#hes.deu.eu
--------
I don't have a small test case for you, but I can point you to the
start of the source trail:
$PTOLEMY/tycho/kernel/gui/ErrorMessage.itcl says:
--start--
# COMPATIBILITY procedure. This procedure emulates the behavior
# of similarly named procedures in pigi, the predecessor to Tycho.
# The window name in the first argument is ignored (since they bring
# up modal dialogs, the window names are not important anyway).
proc ::ptkImportantMessage {win msg} {::tycho::warn $msg}
--end--
$PTOLEMY/tycho/kernel/gui/Message.itcl
says
--start--
##########################################################################
#### warn
# Post a warning message, and return only after the user has acknowledged.
# <p>
# This procedure indirectly calls <code>update</code>, a Tk utility
# that processes pending events, including mouse events. If this
# procedure is called from within an Itcl object, directly or
# indirectly, it may be necessary to take precautions to prevent the
# calling object from being deleted during the call. Because of a
# defect in at least some versions of Itcl, failure to do so can result
# in catastrophic failure of the application (a core dump). In Tycho
# objects, the <code>safeEval</code> method should be used to evaluate
# this procedure or any method or procedure that in turn calls this
# procedure. If the procedure is called from the top level or from a
# Tcl procedure that is not itself called from within an Itcl object,
# then there is no cause for worry.
#
proc ::tycho::warn {msg} {
set name [autoName .message]
uplevel #0 [list ::tycho::Message $name -text $msg -bitmap warning]
return [::tycho::Dialog::wait $name]
}
--end--
tycho::Message is an Itcl class that extends tycho::Dialog, that extends
tycho::TopLevel that extends tycho::TArchetype
Perhaps the easiest way to replicate the bug would be start up tycho
by running $PTOLEMY/bin/tycho and then running
ptkImportantMessage "foo"
in the console window.
It looks to me like this is Itcl code, so the bug could be in Itcl
2.2
Note that Ptolemy 0.7.1 uses Itcl 2.2/Tcl7.6
Ptolemy 0.7.1 is the latest full public release
Ptolemy 0.7.2devel uses Itcl3.0/Tcl8
For details, see
http://ptolemy.eecs.berkeley.edu/ptolemyclassic/pt0.7.2/main.htm
-Christopher
Christopher Hylands [EMAIL PROTECTED] University of California
Ptolemy/Gigascale Silicon Research Center US Mail: 558 Cory Hall #1770
ph: (510)643-9841 fax:(510)642-2739 Berkeley, CA 94720-1770
home: (510)526-4010 (Office: 400A Cory)
----------------------------------------------------------------------------
Posted to the ptolemy-hackers mailing list. Please send administrative
mail for this list to: [EMAIL PROTECTED]
