https://bugs.kde.org/show_bug.cgi?id=358655
Ralf Habacker changed:
What|Removed |Added
Blocks||363891
https://bugs.kde.org/show_bug.cgi?id=358655
Ralf Habacker changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #16 from Ken Standard ---
I am kind of taken back by some of your comments.
Why would you need a test case for valid, commonly used, generic GNU C++
syntax? It seems unnecessary, redundant, and easily recreated.
I see
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #11 from Ralf Habacker ---
(In reply to Ken Standard from comment #4)
> Not seeing it here.
>
> In fact the whole source import process is very rough and is not as intuitive
> as one would expect.
What could be
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #9 from Ralf Habacker ---
(In reply to Ken Standard from comment #8)
> 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
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #10 from Ralf Habacker ---
(In reply to Ken Standard from comment #5)
> I have discovered an interesting phenomenon that affects this situation.
On umbrello start c++ is predefined as standard and opening the
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #12 from Ken Standard ---
OK, maybe we are having a language barrier - not sure.
When talking about "project import" for a Qt project, you cannot ignore the
.pro file - it is the project. Are we redefining "project" to mean
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #13 from Ralf Habacker ---
Git commit 67a97004fc8353544326d4875e3c236813a1bb6a by Ralf Habacker.
Committed on 29/01/2016 at 20:30.
Pushed by habacker into branch 'Applications/15.12'.
Add c++ import testcases for
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #14 from Ralf Habacker ---
(In reply to Ken Standard from comment #12)
> OK, maybe we are having a language barrier - not sure.
>
> When talking about "project import" for a Qt project, you cannot ignore the
>
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #5 from Ken Standard ---
I have discovered an interesting phenomenon that affects this situation.
If the .pro file contains either comments (lines with #) or an
include(include.file) there is a log message that treats it
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #4 from Ken Standard ---
Not seeing it here.
In fact the whole source import process is very rough and is not as intuitive
as one would expect.
I did not mention this before, to keep the issues separate. But whether you
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #7 from Ralf Habacker ---
(In reply to Ralf Habacker from comment #6)
> You are refering to different cases ?
To be able to get a better idea: After importing you will find a dock window
named 'protocol' which
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #8 from Ken Standard ---
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
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #2 from Ralf Habacker ---
Created attachment 96880
--> https://bugs.kde.org/attachment.cgi?id=96880=edit
xmi file with imported header (generated with version 2.18.1)
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #3 from Ralf Habacker ---
(In reply to Ralf Habacker from comment #2)
> Created attachment 96880 [details]
> xmi file with imported header (generated with version 2.18.1)
This file shows that at least with 2.18.1
https://bugs.kde.org/show_bug.cgi?id=358655
Ralf Habacker changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=358655
--- Comment #6 from Ralf Habacker ---
(In reply to Ken Standard from comment #4)
> I did not mention this before, to keep the issues separate. But whether you
> are importing a project or using the import wizard, many things
17 matches
Mail list logo