@Rameshwar

@J-Hilk has given you the necessary code to start from. That's why people type in answers to questions. First try that and verify it works.

Then change it so that it writes on your mainwindow or whatever you want instead.

Only after that, write back if you can't get what you want working.

When building with Qt Creator, you have to disable the QtQuick compiler in the qmake build step. Simply unchecking the checkbox and rebuilding solved the problem.

Hallo.

Wenn Du ausschließlich Qt Widgets benutzen möchtest, so würde
ich vorschlagen, dass Du, z.Bsp., Dein Hauptfenster zwei teilst:
Das eine Unterfenster soll dann die wechselnden Ansichten zeigen, und das andere Unterfenster enthält dann Dein TreeWidget.

Klickt man dann ein Item des TreeWidgets an, wechselt sich die Ansicht im Nebenfenster.

@sirop Vielen Dank für den Tipp.

Ich habe jetzt herausgefunden das DLLs gefehlt haben. Dies habe ich herausgefunden als ich selbst die Anwendung ohne IDE gestartet habe. Da kamen entsprechende Fehlermeldungen. Nach einfügen dieser fehlenden DLLs funktioniert es nun.

Vielen Dank für die Hilfe und an alle ein schönes Wochenende und einen guten Start in die neue Woche.

Grüße
Sven

Vielen Dank @J-Hilk für den Link zur sehr guten Dokumentation was mir weitergeholfen hat.

Vielen Dank auch an @mrjj der auch einen entscheidenen Tipp gegeben hat eben dass es nur mit dem MSVC Compiler funktioniert. Habe beim Installationsprozess von "webengine" auf der rechte Seite gesehen das MSVC 2017 erforderlich ist von daher stimmt die Aussage absolut.

Vielen Vielen Dank nochmals an euch beiden die mir geholfen haben.

Grüße
Sven

@Patrick-Fromberg Agree, it would be good to have the possibility to update after using offline installer to install.
Regarding compilers: you can configure them as well in QtCreator and then select the correct compiler in your Kits.

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

This address is rather suspicious. Please tell me you don't have global QWidgets?

No, I have only a dll with function

extern "C" CORE_SHARED_API QMainWindow * svCreateMainWindow() { return new MainWindow; }

(CORE_SHARED_API is __declspec(dllexport))

@kshegunov said in App crushes when Qt core calls WinAPI's "DispatchMessage" function:

Btw, 0xc0000409 is stack overflow, so be on the lookout for endless recursion.

As I said, QWindowsGuiEventDispatcher::processEvents() is called twice, and I believe those calls are on the same stack level (crush happens in the second call).

@SGaist
Indeed he is
   but if you feed him bugs
after midnight then he goes like

but then you find the actual reason
   for all your problems and then you
feel like

:)

@AndyS said in Any Qt education slides?:

What might be best is to show some of the videos on the website as that gives a good introduction into what you can do too.

In addition to the website videos, there's also a YouTube channel full of Qt goodies: https://www.youtube.com/playlist?list=PLizsthdRd0YykOJsqikaW-OCF3r7OXRB5

@Galbarad so please move this topic to SOLVED state.

Strange behavior, nevertheless.

Hi @aha_1980 ,

If you refer to the Clang Code Model Annotations that are also visible in the editor, then no.

Yeah, I referred to this one. It would be nice if Qt Creators supports this.

I try to do set up a complete build to get the compiler output. Thanks!

@DSpider great! please don't forget to mark your post as solved. Thanks.

As I said earlier, very difficult to get the status ethernet using UDP. UDP is fire & forget protocol. You need to build your own mechanism to monitor the status. It could be simple TCP connection to see if the connection alive with remote server. If not you need to get the interfaces status periodically through QNetworkInterface & check if the interface is up. You can use QNetworkInterface::flags() & QNetworkInterface::IsUp to check the status.

@A123 said in New Errors when moving C++ code to QT Creator:

its been used by others for years and it worked perfectly AFAIK with gcc and clang before I started using qtcreator which complained.

Here's my guess: Previously, the assert() macro was disabled. This caused the illegal code to be effectively "commented out", so the compiler didn't detect it. After the migration, the assert() macro was no longer disabled, so the compiler now sees the bad code and (correctly) complains.

See http://www.cplusplus.com/reference/cassert/assert/. You could make your code work again by defining the NDEBUG macro, but be careful: This will disable all assert()s which might cause other errors to go undetected.

P.S. The compiler is the one that complained, not Qt Creator.

@jsmolka said in Trouble compiling files with identical filenames:

Is there any way to fix that and use multiple files with the same name inside my Qt project? Does it perhaps have something to do with the fact, that I am compiling into a bin dir inside my repository?

Not with shadow building, no. When you generate a bunch of object files in the same directory, the object is named after the source file. So the identically named source's object file will overwrite the previous one (in order of building); it may even happen only partially if you're building on multiple cores.
It's a known pitfall and you should name your files better as people have already suggested.

Define your variables via cpp.defines and use from C++.

@skylendar

you shortened the log, so I can't see the GDB version. Please check these.

Also, GDB must be python enabled, and last the python dumper script must be loaded. Have you checked the directories?

Regards

Another way is to create .dmg file by hdiutil create instead of macdeployqt -dmg .

mkdir ui-release cd ui-release ln -s /Applications cd .. mv $appfolder ui-release/ hdiutil create -volname $volname -srcfolder ui-release/ -ov -format UDZO $dmgfilename

Thank you so much for your helping

@aha_1980 : I just noticed something else: In the log file, there are lines saying "GDB 71101", presumably because it is using v7.11.1 (?!). But I have installed GDB v8.2 in both usr/bin and usr/local/bin. And I've set those locations in QtCreator's options pages for kits and for debuggers. There should be no way for QtCreator to find an older GDB version.

The GDB version in both usr/ folders above is 8.2, confirmed by running via terminal. And I did not find any older stray 7.11.1 versions that QtCreator could be picking up.

Another oddity. Is there any other options page where the GDB location needs to be set?

@Christian-Ehrlicher Thankyou It's Working

Figured out my issue. I just needed to instantiate a QQmlDebuggingEnabler object. Calling QtQml.QQmlDebuggingEnabler() before instantiating my QApplication was enough.

@jsulm we make an installation file for our combined system, including multiple programs sharing some but not other resources. we use an nsi script to manage this. usually works fine. I just missed updating some of the .dll files.

@Ratzz
Thanks for your references.

@J.Hilk
It works ! THANKS :-)

@jsulm
I got this, thanks

My bad, I misread from where the signal came from.

@sergsmi privet !
вы можете использовать QML Shape type : https://doc.qt.io/qt-5.11/qml-qtquick-shapes-shape.html

@Devopia53
It works! , Thanks.

@MikhailG thank u so much sir
i will try.

I know this is an old topic. But I stumbled upon this topic multiple times, but now I got CMake in QtCreator with Visual Studio 15 2017 working. But had to change a few things.

In the Qt kit, I choose:
CMake Generator
Generator: Visual Studio 15 2017 Win 64.
Extra generator: None
Platform: empty
Toolset: empty

CMake Configuration: only CMAKE_PREFIX_PATH:STRING=%{QT:QT_INSTALL_PREFIX}, removed the others

When generating a cmake project, I have to change the resulting Build Settings (for each build configuration).

CMAKE_BUILD_TYPE: Debug
CMAKE_CONFIGURATION_TYPES: Debug

Build steps: choose "ALL_BUILD" instead of "all"

For us this resulted in a working build using msbuild, which allows us to build Wix installers etc. as well, something that cannot be done with NMake Makefiles.

thanks !! . I will look into both of them

It is boost library issue. Looks like you are not using the capture method of boost properly . Look at some examples of boost and fix your issue.