Qt Creator and other tools

I am using VS 2013 and I got a similar message after my last combined WINDOWS and VS update. The only difference: it complained about port 12015. The message appeared once and never again until now. There were no visible problems, so far: build and debugging work just fine. Maybe the WINDOWS update closed some ports (as a security feature) and the VS Add-In does not really need them in what I am using of it.

ah.. found an interesting page here: http://doc.qt.digia.com/3.3/qmake-manual-6.html @VERSION = $$system(grep urgency ../debian/changelog | cut -f2 -d" " | cut -f1 -d\- | cut -c2- | head -1)@ does it..

There is bug for this issue on Qt 5: "https://bugreports.qt-project.org/browse/QTBUG-40168":https://bugreports.qt-project.org/browse/QTBUG-40168 . As I have commented on the issue, I solved it by using a DVI connection instead of using HDMI connection. Thanks for the support. Regards, Varun

Qt Creator F1 context help for CMake doesn't work if you use Qt Creator 3.1.2 or below as the patch for it wasn't pushed in time for its release. As of this writing, Qt Creator 3.2 RC1 has been released which does contain this change, so you can use that instead. Recently, there was a blog post over at KDAB on the subject and it has a link to a generated qch file for CMake 3.0.0. The post can be found "here":http://www.kdab.com/context-sensitive-cmake-documentation-qtcreator/. As for cppreference docs, they have released a new version of their docs which now works (more or less) with Qt Creator's context help. If you need to generate it yourself for whatever reason, there's a link to the utility scripts you need at the bottom of the download page.

You're welcome ! Since it's all clear now, please update the thread title prepending [solved] so other forum users may know an answer has been found :)

May I get some help guys?

Thanks for the help, JHSK and hskoglund. I'd thought I'd narrowed the cause to the C++ and/or Code Analyzer plugins, but it looks like they aren't the source either. I'll try with the Microsoft forums, but I think moving what I've done so far to my linux partition and installing Qt there will be more productive in the short term. Again, thanks for your time! Wilcroft

Hi, IMO the options means that your uncrustify.cfg shall be in your PROJECT. Depending on your project type (QMAKE, CMAKE, ....) you MUST add this file to the files managed by project

Good to know. Thanks!

Well, I'm certainly not an expert, but you did use widget.resize(yoursize)? Some other values might be important, such as the widget.minimumsize, the widget.sizehint and the same value(s) in a layout if you have one set on your widget.

Hi, Looks like there might be something missing, you should ask this on the qt-creator mailing list

Oops! I found it! Someone hinted towards somewhere in Googlespace, it's in download.qt-project.org and I downloaded the 2014 code. I'll check it out. I just have to setup the parameters for my Qt Creator installation (I have VS2010 Pro and VS2013 Express, so I'll have to point to the VS2010 version).

Hi, [quote]I’m wondering if Qt SDK offers opening mht files in Assistant ?[/quote]No, Qt Assistant only opens QCH files. Note: If you want to use Qt Assistant, it is best to write your documentation in the source code itself. This also makes it easier to sync your documentation with your code. See the "Doxygen manual":http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html

I don't know why, but this solution works

Hi, Please take a look at the Getting Started tutorials from Qt Creator and Qt's documentation (Qt Creator first, it will make your life easier)

Right. You need to delete .user file before opening the project. Then qtcreator will ask you to re-run cmake. Also you may try to hide your current setting by moving @ $HOME/.config/QtCreator* @ to some other place. QtCreator will re-create it on first start with default settings.

It's not that simple. qmake.exe has paths, ABI, mkspec, etc., all hard coded in the executable. Run something like "strings qmake" and grep for one of the settings obtained by "qmake -query". They're in there. Specifying a mkspec in that dialog does not do enough to solve the problem. In fact, even though my kit has my Linaro cross compiler set up, it still calls MinGW's compiler and I end up with a Windows binary. The qmake settings can be modified (using "qmake -set"). I tried to take the MinGW qmake.exe that is installed with Creator and change its settings to match those from the Linux build, but this does not work.