After changing a function previously marked private to public, the background parser did not reparse one of my open files which was attempting to call this function until after i made a change to that file. Reproducible: Always Steps to Reproduce: 1. create private function (private: void test();) in header file 2. attempt to call test from another open file(should highlight red for declared private) 3.change private function to public Actual Results: function will still be marked red on the file attempting to call it. Expected Results: background parser should reparse all open files and unmark that function call.
also related to this, the background parser will not reparse a file if it is not the current file when the parser decides to parse it. If you change a function in the header file or add to it and then quickly switch to the cpp file, it will not reparse that header file until you go back to it again.
As I _guess_ this could be related, I'll just add my experience to this thread. In my "not so huge" project, the parser sometimes stops parsing at all for certain files (as described in #371018 it's quite slow to start so that I sometimes don't even realise it anymore when it fails). So currently I have the situation that no matter what I change an #include directive to, KDevelop insists it is the old, correct file that is meant. I'll add a screenshot... This behaviour could explain many other parts where the highlighting isn't working anymore after switching to KDevelop 5 (until now I thought it's a huge mess in my code that the parser simply gave up or so - but here it's pretty obvious). Restarting KDevelop doesn't help. It starts, takes its 5 seconds or so clang salute (see #369164) and then stays like shown in the following screenshot. Even clearing the DUCHAIN cache by deleting the whole kdevelop .cache directory doesn't work (which irritates me a lot ;-) ).
Created attachment 101821 [details] "proof" of kdevelop vs filesystem
After a long testing session, I found the reason for the behaviour in my case (and some other smaller problems :-/ ) which is probably not related to OP's case. So I created a new bug report: bug #371741
Sorry for coming back ;-) But I now have a error-free header file not included anywhere which isn't parsed anymore after some editing (renaming of a class). Deleting the cache won't help either. Just copy/paste the contents to a file2.hpp makes it work again. Is there something we users can do in such a case to gather more meaningful information for the kdevelop developers despite just crying "Won't work!"?
Steps to reproduce are always useful. Unfortunately we don't have the time to look at all incoming bug reports immediately, so please bear with us :) We'll ask for more information when we need it.
Created attachment 103221 [details] Parser bug video Added a video of the bug. In the first part, i show the correct case, what it is supposed to do. the second section i show the bug i'm having with the parser.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
seems to be fixed