RE: [PyCrust] CallTips and AutoComp need work

[Patrick K. O'B. <po...@or...>]

Uggghhhh. Found the problem - missing a try: block in one spot that does an
eval().

---
Patrick K. O'Brien
Orbtech
"I am, therefore I think."

-----Original Message-----
From: pyc...@li...
[mailto:pyc...@li...]On Behalf Of Patrick K.
O'Brien
Sent: Wednesday, August 08, 2001 1:09 PM
To: pyc...@li...
Subject: RE: [PyCrust] CallTips and AutoComp need work

The shell editor contains text and nothing else. I can't do anything
introspective with that text until I turn it into an object reference. That
means there is no way to get a call tip or auto complete list without doing
an eval() on that text. Doing an eval() may have side effects. Or it may
simply fail because the text passed to it is not valid syntax or not a known
object.

At this point, the PyCrust calltip and autocomp do NOT eval() code that
contains a method or function call, such as in your third example below. So
it won't pop up a call tip or autocomp on those. However, in your third
example, it does try to eval('.getText') and that fails, as you might
expect. But the eval() is in a try: block so the program goes on without a
hitch. The result that you are seeing is that this failure inside the try:
block writes an error message to the dos window and I'm pretty sure that has
to do with where the current functions are located and I am working on
restructuring that code.