v2.0: Code completion issues

[spyder-bot]

From [email protected] on 2010-08-29T09:00:22Z

I am working on Ubuntu 10.04/amd64, using python 2.6.

Code completion is one of Spyder's key features - actually the one that made me choose it over other, powerful ide's like openkomodo or boa constructor - it's great! Still, there is room for some improvement:

1. typing backspace or simply hitting "caps lock" (which is something you do often when browsing module/class-level CONSTANTS for instance) closes the popup list, forcing you to backspace down to the last dot and re-type it, and it's very frustrating. I suggest that the popup should be left open, at least unless one has just deleted the dot.
2. It seems that code completion doesn't work when typing if: "if a == b.c(doesnt, show):" - while it correctly shows when typing assignment: "r = b.c(this, shows)" - why?!?
3. the rope tooltip sometimes appears briefly and then disappears when typing 'somefunc('.
4. it would be very useful if the tooltip would also show up when hitting commas following somefunc( - as in "r = c.d(a, b,...". I find myself often re-typing the "(" just to see the tooltip again and again.
5. Sometimes there is some error in the sorce (all too often a missing colon :-), which effectively prevents code completion and tooltips from showing up. Would it be possible to let the user know that? (like a red flag) - not everybody is able to guess there is some error, let alone that this actually breaks code analysis.
6. keyword highlighting is a wonderful feature to have, and I wouldn't disable it, but I find it very annoying when I happen to pause the cursor near a 'self' keyword. It then highlights hundreds (even thousands) of 'self''s all over the file... I would rather have it highlighted in the current function, if at all.

Thank you for your time and effort. Great job!

Original issue: http://code.google.com/p/spyderlib/issues/detail?id=319

[spyder-bot]

From pierre.raybaut on 2010-08-30T10:01:49Z

1. fixed as for the 'caps lock' key. But regarding the 'backspace', I can't reproduce the behavior you reported (when I'm hitting 'backspace', the combo box is still visible, and it's hidden only when removing all chars after '.')
2. I can't reproduce this bug: could you please give more details, a test case?
3. & 4. I'll think about it when I'm confronted to this situation (I already have)
4. There is a parameter in 'rope' that is maybe related to this. I'll have to do some tests. Could you please send me a test case on this too? (it would save me some time)
5. Fixed

Summary: v2.0: Code completion issues
Status: Accepted

[spyder-bot]

From [email protected] on 2010-11-29T07:49:20Z

I am also running into issue #3 and 4. The rope information will stay visible until I start typing. This greatly reduces it's utility. I constantly find myself moving the cursor back over to the opening parenthesis, deleting it, and retyping it to bring up the rope information again. Maybe the temporary solution is a hot key similar to the code completion hot key?

[spyder-bot]

From [email protected] on 2011-04-04T09:32:45Z

Is there any progress on addressing Number 4? I'd really like to see this be addressed in some fashion.

[spyder-bot]

From pierre.raybaut on 2011-04-27T04:50:47Z

FYI, problems related to the fact that the tooltip was hidden too soon have been solved (number 3 & 4). The arguments aren't highlighted but at least the tooltip remains visible (BTW, this was the original behavior, so this was a bug!).

1. Another issue has been submitted on that subject. I'll take a look at it.

Status: Fixed