This is not helping
-
First - I no longer have split screen so I can see the screen shot I have posted here nor the text I am typing.
(suggestion to get the split screen back would be appreciated )Without that - here is a short version on the "complaint".
I do not know what is this new ( to me ) feature of (what) called, but it does more harm then good.
In the attached example , this FEATURE (?) which I cannot currently see , perhaps AFTER I post it , adds "period" at the end of the line before I am done adding the code and I have to jump thru hoops to get rid of the "period" I have NOT added.
So - thanks for nothing , but constant nagging BEFORE my add is fished.This is not the only weird issue with this "feature" and I do not feel as a user I have to "post a bug" .
So do not suggest to do so.I am using Qt to code NOT to do vendor's QA.
[edit: fixed link in coding tags SGaist]
-
@AnneRanch said in This is not helping:
Am I going crazy or is this normal ?
I cannot remove LAST empty line!Stop your debugging session first, then remove the line.
-
Moved to 'Tools' since it seems to be a complaint about Qt-Creator (at least I think...)
-
@AnneRanch said in This is not helping:
suggestion to get the split screen back would be appreciated
https://doc.qt.io/qtcreator/creator-coding-navigating.html#splitting-the-editor-view
-
Am I going crazy or is this normal ?
I cannot remove LAST empty line!
-
@AnneRanch said in This is not helping:
Am I going crazy or is this normal ?
I cannot remove LAST empty line!Stop your debugging session first, then remove the line.
-
"This" is still not helping...
BEFORE build process is started warning - it is disabled in.pro file(!) - is posted , AFTER build is finished "issues" are posted.Simply put
why would one worry or used as usable information that variable is not used (!) instead of getting a real error BEFORE build?
It used to work that way....
PS Does this nagging feature have an official name ?
(Yes I know how to disable it ) -
@AnneRanch said in This is not helping:
why would one worry or used as usable information that variable is not used
you may want to look at this explanation for instance...
(Yes I know how to disable it )
I hope you don't disable the warning (i.e. -Wno-unused-but-set-variable) but rather you remove the actual unused code
-
@AnneRanch
Since you don't seem to like the warnings/help produced by the clang code model, why don't you switch it off and get less of them?why would one worry or used as usable information that variable is not used (!) instead of getting a real error BEFORE build?
The warning on the line shown in the editor ("value not read") simply has nothing to do with the error ("undefined reference") you receive at link time. They are two quite separate things. And there is no chance that the link error would occur/be known at edit time, it could not be known before build since it is a build (link) error.
-
