Just wanted to update this thread, and ask NathanR if he’d looked at the samples that I sent or had any further ideas.
This is one of this annoying things that I pick at every once in a while. I notice that others here have reported somewhat similar things happening with the UI.
I get the feeling that there must be something odd in the modules (files) I’m trying to edit, but what I’m really wondering is whether there’s any sort of instrumentation that I can enable to try to make sense of this. I’ve tried the latest nightly build, as well as a test build of V9 - with the same results.
I also realized that I hadn’t installed a library that I use (boto) on my local machine, so I did that. I now get (in my test module) the calling info for that API, which is helpful and seems to indicate that more expected functionality is working.
But today’s test is to start a new module, enter some meaningless code, and test whether I get calltips with info about a function that I’ve just defined - and it works - and then I paste in a class from one of my “real” files and while I get autocomplete (for the symbol) I don’t get any tooltip for that same function, even though I’m entering a nearly identical statement to the one immediately above that did work.
Also installed pylint while I am at it. No change to this behavior.
One more weird UI thing: I’d moved the code panel to the right pane early in my use of Edit, and I’ve been noticing that when I start KIDE with several open tabs from the last session the Code panel doesn’t populate - it just stays blank. This seemed to happen often, and I switched it back to the left pane and it seems to work more reliably.
And one more observation: I noticed some discussion about performance on Mac OS X. KIDE isn’t the snappiest app that I run, but my MBP (primary development machine) is pretty old, and nothing really runs fast. But - I’m wondering whether the problems that I’m seeing might indicate a resource issue that isn’t being detected by the app. I say this because I do see certain things take quite a while… I think using an old workstation for intensive work is sort of my issue, but it would be interesting to understand whether some of the functionality in question does time out, and that I lose this functionality as a result. (Note that I have verified the particular issues with missing calltips on another machine, also fairly old but with 8 cores and SSD.)
Sorry to be so aimlessly emitting things, but like I said, I wish I could be happier with the application, since in so many respects it’s a real help. Thanks for reading…