Qt Creator and other tools

Mayb only through qDebug()? Although that would be stupid.

ok - changeglog is quite clear (-; it is possible to build Creator 3.2 against Qt 4.8.x bq. Compiling Qt Creator 3.2 Prerequisites: Qt 5.3.1 or later (with restrictions also Qt 4.8.x) NOTE: confirmed: Creator ver 3.2.2 is building against Qt 4.8.5 without a hitch and working working with full scrolling speed e.g, supporting native rendering option

[quote author="SGaist" date="1418382303"]I meant an assert in the library you are using[/quote] I have no sources for external library. I using this library from MSVS and have not any questions. I think it's matter in differences debug / no debug modes.

You're welcome ! Since that point has been cleared, please update the thread title prepending [solved] so other forum users may know a solution has been found :) Happy coding !

I get this answer somewhere else Thomas Hartmann says: December 10, 2014 at 15:36 If you need complex backend data or models, then you can do what is described here: http://blog.qt.digia.com/blog/2011/07/28/mockup-data-for-the-qml-designer/ But with Qt Creator 3.3 we introduced a new ui.qml file format. In this case your code is split into full QML and a subset (in the .ui.qml file) for the designer. Then you can define any values and even models in the .ui.qml file and overwrite those in the qml file that contains the implementation. See: http://doc-snapshot.qt-project.org/qtcreator-3.3/creator-quick-ui-forms.html

Sorry, I missed the first one. Nothing wrong, IIRC it's a question of buffering but I don't remember the exact details

You can modify the mkspec used in Preferences -> Build and Run -> Kit -> select the kit you want to use

I managed to solve my problem. The fact that earlier I manually added fonts from Windows to the Linux Mint . Qt5 processes these fonts incorrectly (I don't know why). After removing the added Windows fonts problem is solved.

Hmm... seems quite a waste of purpose having a subprojects template just for having all sub-projects grouped together... I would have found it very useful if I could use the main .pro file to define some general includes, variables... well anyway, thank you very much for answering, andreyc :)

Welcome to DevNet. AFAIK there is no such feature in qtcreator. When I'm getting lost among opened files I use "Close all files except visible". Also you can open a feature request on https://bugreports.qt-project.org/

Can you show the content of your pro file ?

Removing Options -> C++ -> Code model -> Ignore pre-compiled headers option (this is set by default) seems to fix the issue - code completion and parsing is smooth now. I don't use PCHs in my projects explicitly, so don't know whether it influences its supposed aim to improve performance.

It's actually not a c++ problem as it defines nothing about the ABI. It's the vendors that don't get along and don't maintain backwards compatibility. But that's a curse and a blessing at the same time. Managed c++? You mean the abomination of C++/CLR? I'm almost certain it would be impossible, if not for the sole share of 3rd party libraries required for starters. OpenGL, ICU, DirectX, Webkit, all the platform specific APIs, python and perl needed for building... nah, forget it. C++/CLR is dying anyway. Very few people are interested in it these days. Certainly not Microsoft anymore.

You can find several post on this forum for that GL error. You are missing the OpenGL development libraries. Qt's default projects run with the minimal amount of code to get a window/widget

Thanks but this was bug and he is already fixed in upcoming release.