Qt Creator and other tools

I tried that. I have about 600 projects total, and I get one long list. Its a lot nicer to go to GeneralApps -> UI. I think what I might do is put all the .deps under one include file in each directory so I only have two includes in each project. I could live with two. Its the ones with 15 or 20 that look really bad.

Hmm... There was another .pro file in the sub-directory for the library.... I modified the path there and now all is OK. Just feeling a little bit stupid here... Furthermore, the mypackage.path I indicated above is wrong, since it should have been the remote path while I put in the local path... Just another incomprehensible lapse of judgement here of course, because the right path is mentioned just below there, in the target.path... It would have been useful if the output of the deploy step would also mention to which remote path is uploaded the files. Thanks for letting me find it out by myself^^

@SGaist thanks. I'll try it there.

Great. Moreover, singleton is a better approach for me. Because I could make the code as a module and share between different projects. I just make it available at github: https://github.com/benlau/fontawesome.pri

We create those mockup types internally, so no files are created. This just stops the engine from reporting errors. You could also use QML_DESIGNER_IMPORT_PATH to define an import path for manual mockup files. Before we create the mockup we check, if the type is already available and only create the mockup if it is not.

The problem may have been OpenGL-related: when I disabled my VM 3D acceleration (Parallels 12.0.2 on macOS 10.12.1 Sierra) things got better.

@Chris-Kawa Thank you very very much! That is Exactly what I needed. Very helpful.

The whole bug cuzed by declaration of function in the header file , i wrote ":" insted of ";" :)

@MrLibya Qt only destroys objects which have a parent derived from QObject. Most of the objects you create do not have a parent. And again: why do you use pointers? In your case there is no need for pointers and heap allocation via new at all.

@SGaist Isn't that because of vsaddins? Probably the stripped stems from there somehow. Unfortuntely Tobias message vanished in the forum's nirwana.

@koahnig Basically two problems on my side. .moc is not generated for every dialog as I thought. I got confused by name convention. moc_*.cpp are being produced. However, I had made another stupid error before. Accidently I had placed my test code into the contructor of the testing class and not in the routine testCase1() as required. However, since I had no problems from the being, I did not pay attention to this details. After moving the code to testCase1() also the test returns from my widget are monitored.

@halil-sogut68 Google is your best friend here, I guess ;) AFAIK you simply use any command driven SVN or Git installation at your computer. There is also the creator documentation for it.

Answering my own question for future reference: Despite having a 100 % standard installation, I need to specify the "Qt sources" under "Debugger->General"

Hi In what way "cannot find any." ? In the Welcome screen/plugin under "examples" ? [image: 3x28Qm.png] It the welcome plugin happy? Showing recent projects etc?

I remember experiencing performance issues on QtCreator 3.5.1 when I had expressions. Have you tried clearing your debugger expressions ? No idea if it's related to your problem but worth checking! Check this post: http://galfar.vevb.net/wp/2014/problems-with-cdb-debugger-in-qtcreator/

Its the way MIngw creates its debug code. It puts it inside the the dll making it 20 times(or more) bigger then a release version. The relevant dll's (that causes a problem) have in fact no resources. It is pure algorithms. MS puts the bulk of debug stuff outside the dll making its size more managable.

@SGaist i got false , anyway i found this method and it works query.last(); numRows = query.at() + 1;