https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #8 from Ken Standard <ad...@arrl.net> ---
OK, I will be "more specific".
Your #1: This will always be the case with PIMPL coding style. As I mentioned;
after removing the comments (lines with #) from the .pro
after removing the include(myfile.pri) line from the .pro
after modifying the filter patterns in the import Wizard
after selecting specific files in the files list
the private classes were imported properly appearing as private classes in the
logical view list of classes and with the forward declared items as a privately
declared class in the imported class.
Your #3: I made no mention of any other file having an include except for the
.pro. In that context I mentioned it reported as an error in the syntax. This
is not a proper response by the import wizard since it is completely valid for
Qt projects. Not only that, the # mark in the .pro file is also treated as an
error anywhere it appears. This also is not valid since it is the designated
comment mark for Qt project files. If a C++ comment ("//") appears in the code
it too is not ignored as it should be, but treated as a code error as well
being reported in the wizard import log as a syntax error. Interestingly, a "C"
style comment (/* */) does not render an error and IS ignored.
Comment 7: I find no dock window, list, or other window, named or titled
"Protocol". The import wizard has a "Logger" window and the main window has a
"Log" dock window. There is also no menu choice to view any "Protocol"
information.
--
You are receiving this mail because:
You are watching all bug changes.
