Hi,
AFAICT the F1 help won't work if there are syntax errors or when the
code model can't correctly parse your file. If the syntax highlight
doesn't work either, then it is good guess that there is some syntax
that it can't parse.
Which code model do you use?
These days I have good experience
Maybe it thinks that it's a C header and not a C++ header, and that's why. Just
a wild guess.
On Monday, 7 May 2018, Jason H wrote:
> I use a copy of the Qt style and it's all been good up until 4.6.1
> I use tabs with a tab size of 4 indent 4, Tabs-Only for C++, with clean
> whitespace on
Hi Alexey,
Are you sure it is running as a Wayland client and not under XWayland?
On Tue, 2018-04-24 at 11:22 +0300, Alexey Min wrote:
> I'm using Qt Creator (compiled manually with system Qt 5.9) with
> Plasma 5 Wayland session with no problems.
> Except one, multi-sequence hokeys don't work
Hi,
I'm using latest Qt Creator 4.6.0 on Fedora where I run a Gnome Wayland
session (the default in newer Fedora releases).
Out of curiosity, I poked around and was surprised to notice that Qt
Creator runs inside XWayland, despite Qt's Wayland support. So I tried
to run Qt Creator as a Wayland
Hi,
Just noticed that with the latest version of Qt Creator the memory
usage numbers went up.
Currently I get ~400MiB for qtcreator and ~450MiB for clangbackend.
This seems to slowly go down after I close some source files, though it
takes time (guess it keeps them in cache for a while).
Are
Hi,
I'm working on a project which uses the Qt coding style.
Does you guys have a .clang-format config file for this style which I
can use with Qt Creator's Beautify plugin?
Thanks,
Timur
___
Qt-creator mailing list
Qt-creator@qt-project.org
Hi,
When enabling some clang-tidy checks (notably modernize-*) in Qt
Creator 4.6.0, I get the following, repeatedly:
2018-03-29T12:55:55 Clang Code Model: Error: The clangbackend process
has finished unexpectedly and was restarted.
Is there a way to debug what exactly is the problem?
Thanks,
Hello Aleksey,
I think the bug report is about something else entirely.
Regards,
Timur
On Thu, 2018-03-29 at 13:14 +0300, Aleksey Kontsevich wrote:
> https://bugreports.qt.io/browse/QTCREATORBUG-18757
> I have gcc 7.3.1 on my machine however still have this. Probably
> depends on gcc Qt Creator
Hi!
I upgraded to Qt Creator 4.6.0 and was happy to see all the stuff that
went in. However, it now dislikes the Q_OBJECT macro:
warning: unknown warning group '-Wsuggest-override', ignored
Looks like another disparity between gcc and clang warning options.
I guess it somehow picks up this:
Hi,
Creator confuses the AltGr key (typically found on European keyboard
layouts) with Ctrl+Alt.
For example, when I want to type an opening bracket { on a Hungarian
keyboard, I press AltGr+B, however Qt Creator interprets this as
Ctrl+Alt+B which is hooked to a build shortcut, so something else
On Mon, 2018-03-05 at 14:23 +0100, Tobias Hunger wrote:
> > As an aside, qmake is going to be deprecated eventually in favour
> > of
> > Qbs, so if you start with Qbs, your work is likely to me more
> > future-
> > proof.
>
> I am not aware that this decision has been made yet: It's still up to
>
Hi,
Indeed this sounds like something you could do with a heavily
customized Qbs project file, using custom rules and similar. Perhaps
try asking on the Qbs mailing list about what you are trying to
accomplish and what specific issues you are facing.
As an aside, qmake is going to be deprecated
I don't have a high DPI display, so not sure if we have the same
problem or not.
I just realized two things:
1. The official Qt installer didn't install the Wayland platform
plugin, so I think Creator must have been running under XWayland.
2. The issue is no longer present after logging out and
On Tue, 2017-10-17 at 19:53 +0200, Elvis Stansvik wrote:
> > > > What do you mean by "not testing the code exactly as shipped"?
> > > > When
> > > > you include the cpp file (or just compile the same file into
> > > > your
> > > > project), why isn't it the same code as shipped?
> > > > Sorry for
> > > > There is another way, and it's used in qbs I believe, that is
> > > > option 2:
> > > > #include "Foo.h"
> > > > #include "Foo.cpp"
> > > >
> > > > class FooTest: QObject
> > > > {
> > > > ...
> > > > }
> > > >
> > >
> > > The downside I guess that again, you're not testing the code
>
Hi,
> Well, actually there are 24 votes.
I guess that's because now it has been mentioned and click-baited on
the mailing list. :)
> I see two possibilities: either the code model is already able to
> deduce
> the correct type for auto, then it should be quite easy to generate
> the
>
16 matches
Mail list logo
