Unsolved Help, JSON checkbox "include QObject" in C++ class wizard does not work for me
-
Long time (years) I was unsatisfied but content about the behavior of my QtCreator, where, when I choose New source file->C++ class, I am unable to check checkbox "Include QObject" (and any other in this form) even when I select QObject (QWidget etc. as appropriate) as the base class. By "unable" I mean, that if I do click that checkbox, very shortly some mark (too fast to be sure whether cross or check mark) appears in the box and disappears again in instant.
I expected this to be wip, and quietly waited for some upgrade, which will fix this. It can be workarounded quite easily if one just do not forget to add respective #include manually...
However today I moved forward towards creation of own JSON wizard based on that C++ class wizard copy and found, that in the official examples of JSON based wizards there is cited exactly this C++ class wizard, even more this "Include QObject" checkbox, so I got feeling it could be just me and my installation (Linux <censored> 4.8.0-1-amd64 #1 SMP Debian 4.8.7-1 (2016-11-13) x86_64 GNU/Linux) having continual upgrade history since Woody was the testing one... I am proud to be able to maintain production environment continuously so long, even over many hardware transitions, however this can time to time cause, that some historical artifacts remains in place and blocks the way.
My question is: is there something (command line parameter to set, internal variable to check, stand-on-your-head attempt ... whatever) I can do to elaborate, what is going on (and blocking the checkbox from simple on/off on each click), hoping this could lead to some fix? I would be really really excited if I could have got this C++ wizard (I use routinely in my work) to it's full design power.
Thanks for any advices.
-
@pmendl I think you should ask this on QtCreator mailing list or file a bug. This forum is for Qt users.
-
Hi
i use the wizard a lot and im not sure i ever saw what you describe.We are talking about the Define class dialog ?
"appears in the box and disappears again in instant."
I try to click it on / off and such. Nothing extra happens.
Ps. Having same linux since woody is cool.
I have a knoppix 3.3 but i have cheated since its virtual. :) -
@pmendl said in Help, JSON checkbox "include QObject" in C++ class wizard does not work for me:
Long time (years) I was unsatisfied but content about the behavior of my QtCreator, where, when I choose New source file->C++ class, I am unable to check checkbox "Include QObject" (and any other in this form) even when I select QObject (QWidget etc. as appropriate) as the base class. By "unable" I mean, that if I do click that checkbox, very shortly some mark (too fast to be sure whether cross or check mark) appears in the box and disappears again in instant.
Try running Qt Creator on a different computer. Does it work?
It works fine for me on Windows 8.1 x64, running Qt Creator 4.2. When I select
File -> New File or Project.... -> C++ -> C++ Class
and select "QObject" as the Base Class, the dialog automatically ticks the "Include QObject" checkbox. I am also able to tick/untick all checkboxes on that dialog. -
@mrjj said in Help, JSON checkbox "include QObject" in C++ class wizard does not work for me:
We are talking about the Define class dialog ?
Definitely we are talking about what your picture shows. For me "something" unchecks the Include... boxes immediately I do check one of them with mouse click.
I have filled bug against QtCreator and (a bit to my surprise) it was accepted. So you (and any follower) can follow the progress there:
https://bugreports.qt.io/browse/QTCREATORBUG-17503 -
Try running Qt Creator on a different computer. Does it work?
Would love to, but don't have second linux instalation ready around. And moreover I would like to fix it on my main production desktop comp anyways...
-
@pmendl said in Help, JSON checkbox "include QObject" in C++ class wizard does not work for me:
moreover I would like to fix it on my main production desktop comp anyways...
Definitely, that is the best outcome. I suggested trying another machine as the first step to troubleshooting.
Thanks for submitting the bug report; this will help ensure that it's fixed for everyone. It looks like the issue is platform-specific.