@sierdzio Thank you very much!

https://bugreports.qt.io/browse/QTBUG-87735 bug fixed) Fix Version/s: 6.0.0 RC

@Chris-Kawa Thanks, it works !

@mzimmers If i iterate over the interfaces like in your script, then it works with no problem :) Running on windows :) When using only the QHostAddress::Broadcast I get the wrong broadcast addr. I too think it is strange, but this is no issue for me, as it's always simple to determine the right address by code or manually :) just strange as you say :) Anways, off to new issues :D

I posted this Question on SO as well, who directed me towards a logger which made it really easy to see what was up and lead to an easy fix. Heres a link to the question if anyone would find it helpful: https://stackoverflow.com/questions/61035096/attempting-windows-deployment-exe-file-not-opening-with-no-error-messages/61036646#61036646

I see, thanks for the response. I stumbled today on an old thread where user wanted the same font rendering as in Photoshop. One of person responding said that they made their own wrapper of FreeType. I guess I will try to render icons using that and see where it goes. Not gonna mark it as solved for now though, maybe someone will stumble on it with some experience.

@bdfyy You can use this tool: https://github.com/JKSH/QtSdkRepoChooser

@JonB Not a big viewer at all. viewer is a simple QGraphicsView containing a QPixmapItem which is continually updated through another slot taking a signal from the camera thread every time it has a new frame, at 60fps. Part of the issue seems to be with the debug build, which is obviously a fair bit slower than release. In release it doesn't really seem noticeable, though I imagine it might be on a slow system. Still, I do find the asynchronous behaviour of raise() interesting. I tried looking a bit at the source code, but didn't really get anywhere. Because it's not a problem in release, I guess I'll just leave it be for now. Thanks for the help, though, much appreciated.

I reply to myself, just in case some else has the same issue. Switching the Jenkins build slave from Windows7 to Linux (Debian 10) has reduced the APK build time from 40 minutes to 8 minutes! Yes, my project is relative big ;) Regards Fabrice

@JDePedro Ok. I found the cause why I was not getting anything QML related from the tool. My widget is not in the exe file but in a DLL so I had to specify the dll instead. But the list of files the tool is getting is huge compared with the one I got by doing the process "manually" and includes most of the .qml files. So my doubt is, do we need to deploy all this files with my application? is not enough with the dlls???

@fcarney I can't beleive I missed your question. Comparing with Heob, Deleaker provides more features like taking snapshot at any moment, and comparing them later. Besides heap allocations, Deleaker also tracks COM/ActiveX/GDI/USER32 leaks etc.

Hi @ivec Is it normal that I needed to select the compiler manually? No. but please select the C compiler also. And how can I enable the use of a debugger to step through my program? You need to install the Debugging Tools for Windows, included in the Windows SDK. Due to licencing, this is not possible otherwise. Regards

@JonB Noooo... I did not understand that the enumeration of multiple paths in the Windows example referred to a list. Now I know :o) thanks.

@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).

what is your suggestion about server app design ? People usually refer to "server app" as "middleware" or "web application". There are tons of web frameworks and ORMs for various languages including Java and C# on "enterprise" side and scripting languages (pphp, python, perl, ruby, node.js). C++ is not really convenient language here. As for protocol, if you are not pursuing real-time data processing with lowest possible latency, it makes sense to use REST API on top of HTTP, so that on server side you have the most typical "web app" with ORM inside and REST outside, and on client side you can easily add web client if needed, and even if not, you get some additional convenience as compared to e.g. RPC over plain TCP

Hi, An educated guess is that the second case is handled by the window manager (the decoration is not done by Qt). One possible thing to do would be to check the screen resolution in your method and try to adapt to that.

@smhrambo deleting the *.pro.user file often helps when you do such moves...

@SGaist Thank you inform about me QtSingleApplication class. I will modify code and use QtSingleApplication.

There is a way to force an external window to become part of a widget, but the API isn't really meant to be used this way and there are multiple issues: https://bugreports.qt.io/browse/QTBUG-45275

@wrekler ok. Im not sure what system buttons are. But yes, its most likely there are bugs as its pretty involving across platforms to support such decoration less window.

@JonB sorry for long reply debug size is 29.5M release size is 18.3M Free memory always a more than needed PC have 16Gb ram. Also i checked swap, swap is newer used for last days. So problem is not here. Next step i will check all dlls one by one in tes Win32 pure C application, maybe problem is here. no cpecific initial code ... but as u can see a lot of dependencies.. In linux exist LD_PRELOAD key but there is no solution for windows i found. Thanks for response, if i found any solution or reason i'll report it here. Cheers.

@Natalya if your issue is solved, please don't forget to mark your post as such. Thanks.

For sake of completeness here is the answer from Qt developers (in case someone reads this and has the same issue): http://lists.qt-project.org/pipermail/development/2018-April/032630.html Unfortunately the reason why it was done in that way is still a mystery but it seems that the hook code can be safely removed

@aha_1980 i cleaned my old project build tried it again. The build is successful but when i try to run same error as mentioned above. any changes : just uninstalled Qt5.9.1 .other than that nothing much. this is my compiler tab if it helps any !! p.. i have downloaded windows 10 SDK too now there is no triangle on msvc 32bit one but the problem still remains :/ .

Could you show full output of cmake? Did you install libsqlite3-dev package and cmake reports that sqlite is not found? That does not make any sense

Hi Do you really need that many kits installed ?? Desktop QT 5.6.2 MinGW 32bit -> can make normal win32 apps in 32 bit. Run on win 10 64 bit too ( as 32 bit) Desktop QT 5.6.2 MSVC2013 32bit. -> 32 bit, you must install compiler yourself. VS 2013 ONLY ( runs on 64 bit too) Desktop QT 5.6.2 MSVC2013 64bit -> 64 bit, you must install compiler yourself. VS 2013 ONLY ( runs ONLY 64 bit ) Desktop QT 5.6.2 MSVC2015 32bit -> 32 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs on 64 bit too) Desktop QT 5.6.2 MSVC2015 64bit -> 64 bit, you must install compiler yourself. VS 2015/17 ONLY ( runs ONLY on 64 bit) Desktop QT 5.6.2 for Universal Windows Patform 32bit Not a Desktop app. WinRT only app Desktop QT 5.6.2 for Universal Windows Patform 64bit Not a Desktop app. WinRT only app Sounds to me you can just use mingw. for both 32/64 bit unless you want app to be 64 bit ?

@raven-worx I have also test the Registry Key changes, but doesn't have any impact. By the way, I just realize that the XP build of my application is using ANGLE (because OpenGL is not supported) and Windows7 is using OpenGL. By forcing Windows7 to use ANGLE, TeamViewer is working also with Windows7 :) QCoreApplication::setAttribute(Qt::AA_UseOpenGLES); qputenv("QT_OPENGL", "angle"); qputenv("QT_ANGLE_PLATFORM", "d3d9"); Thanks a lot for your time Regards

For example: QCameraImageProcessing

@VRonin said in QCA no Makefile: also, if you are using MSVC you have to tell cmake to generate makefiles instead of project files. Pass the -G "NMake Makefiles" arguments to your cmake call You sir, have saved me. I can't believe they don't specify that in the guide (it also uses MSVC, so idk why there wasn't the same problem). I've run into some trouble while building, but that can/should be its own topic. @VRonin said in QCA no Makefile: Slightly related, is QCA supported and updated? The last thing you'd want is to use an out of date cryptographic library. I normally use Crypto++ but libcrypto of OpenSSL is also very good (if you don't mind messing with C) It is still active, looking at the the git (https://cgit.kde.org/qca.git/) the last commit was in 2017-09-30 (some months ago, but it isn't dead). I had also been looking at Crypto++, but ended up settleing for QCA for no pacticular reasons. And I wouldn't mess with C, I'm still even just a C++ newbie afterall ;) QCA can also use OpenSSL btw.