When using the 3rd party libraries such as JUCE for example: you include 1 header file, which names a namespace, and then includes a whole bunch of header files. But when this happens, KDevelop "forgets" there is a namespace. So code completion, CTRL+, and CTRL+. lookups of parameters, ...all that stuff fails to work since KDevelop doesn't know about the right namespace. Here is an example (again with JUCE): > namespace juce { > #include "misc/juce_ColourSelector.h" > #include "misc/juce_SplashScreen.h" > #include "misc/juce_SystemTrayIconComponent.h" > } // end the namespace All of the classes, enums, typedefs, structs, etc..., defined in all of those .h files should all be in the juce:: namespace. But as far as KDevelop is concerned, they're not. This is my code that correctly compiles and links: > juce::SplashScreen::show( ... ); But as far as KDevelop is concerned, if I want to be able to use completion, or to press CTRL+, to see the class definition, my code should be this: > SplashScreen::show( ... ); While I could insert a "using namespace juce;" at the top of all my code, that somewhat defeats the purpose of using namespaces to prevent name pollution and confusion. Reproducible: Always Steps to Reproduce: 1. namespace foo { #include <bar.hpp> } 2. any classes defined in bar.h should be prefaced by foo:: 3. Actual Results: KDevelop will underline in yellow any foo::bar classes, and refuse to do code completion, as well as CTRL+, and CTRL+. Expected Results: KDevelop notices that bar.hpp was included within namespace foo
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue 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!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!