@JKSH , @J-Hilk
Pointer size is increased to 64 but integer size remains 32 on today's common 64-bit desktop architectures.
Yes, now I vaguely remember reading this, I am glad @J-Hilk shared my mis-assumption!
You seem to have installed the Qt visual studio edition.
You need to download and install the compiler from microsoft.
Its not included as thats forbidden.
The MinGW version has a compiler and debugger included.
So Make sure you ONLY install the Qt where you have compiler installed.
If you really dont care and all you want is to use Qt to make Desktop apps
then only install the mingw version and nothing else.
Installing ALL takes up lots of space and give more room ffor issues.
You can just include the wanted .cpp in the .pro file or
make file or what you use to compile. You can also link it into the porject as an .o file. However, if you have a main in the new .cpp that wont work as
there already is a main for the qt app.
Im not sure what you mean by
"while executing this object file getting the result in command prompt ,not in vnc platform.."
The post is already a few years old. However, there does not seem to be any solution. We started using FASTBuild for our qmake-based project. Setting it up for the first time is quite involved. We managed to get it running anyway. I cleaned up our FASTBuild setup for use as a template in other projects and put it on GitHub: https://github.com/SimonSchroeder/QMake2Fastbuild
Currently, the setup is for Visual Studio 2013 with WinSDK 8.1 and Qt 5.9.1. It is mostly modular, such that it should be quite easy to adapt it to different versions of VS, WinSDK and Qt. It supports *.ui files, mocables and resources files. Most of the necessary information (files in project, defines, include paths, ...) can be generated through 3 scripts. Only libraries have to be setup by hand in the FASTBuild configuration files.
The batch scripts are also easily portable to Linux. For an appropriate setup of compilers you can have look at FASTBuild's own FASTBuild files.
I hope this helps anyone. Please let me know if you were able to successfully use the files provided on GitHub. If you add other versions of VS, WinSDK and/or Qt please consider to contribute to the repository.
@supratik123 said in QUDPSocket in bound state:
client is returning the number of bytes written even when the server program is not running.
Is it something different from Connected state.
Since UDP communication is stateless I don't see what should be wrong with this.
yes Iused the full path,
what ever I build and cross compiled ,i am able to run examples in vnc platform...
but i want to build and cross compile qt with eglfs platform,for that any links?....
@SGaist said in What does it mean when an entire function is a slot?:
Technically speaking, emit is replaced by nothing (take a look at the macro). However, it does make the code more understandable with regard to what should happen at that point. It make also clear that you are calling a signal.
In other words...
emit mySignal(); // 
mySignal(); // 
...  and  are exactly the same from a compiler's point of view. However,  is clearer to a human reader.
@BoboFuego said in How to use anti-aliasing on QGLWidget?:
how can I add MyWidget.h as promoted class for it in the MainWindow constructor?
Promoted class won't allow you to pass parameters to a constructor. Just don't add it in the designer at all.
Lets say you've got this designer_widget as a central widget of the mian window in the designer. Just delete it entirely and add it in code:
MainWindow::Mainwindow(QWidget* parent) : QMainWindow(parent)
MyWidget* gl_widget = new MyWidget();
Fix worked great, was able to generate the makefiles I needed.
In \msys64\mingw32\qt5-static\share\qt5\mkspecs\common\windows-vulkan.conf changed:
But this is "Qt Development" forum no? I don't know that it's a bug, I think it's Apple and was asking in case there was just a config or some other thing I had to do to get around it.
I do have an update. The problem is the new SDK. If I go back to a carbon copy backup I have with Xcode 10 (therefore 10.14 SDK) and build, I can run the built package in Catalina too. If I build on Xcode 11 (so SDK 10.15) it builds and runs on Mojave, but has the crash on Catalina. The problem appears to be a bug in SDK 10.15, or a compatibility issue between Qt and SDK 10.15
@JonB Our problem is similar but not same. In both situation, data is there, inside block. But he tries to cast serialized binary data to a QString, that's why he cannot see the string. He should have used >> operator to create QString from QDataStream. Actually I did like that but somehow QString ate all data inside block.
If you check binary representation of block there is 1A before first letter 's'. 1A is aqual to 26 in decimal. My string sample string has 13 characters. 26 shows byte count probably.
Actually this is mentioned in Qt 4 serializing page but not in Qt 5 page.
I thought >> operator of QDataStream does this job for us but it seems it doesn't. I need to handle this situation by myself it seems.
OK, and that's good, but for anyone else reading this the point about the file paths means that the "correct"/"at least preferable" way would pass those argument paths as:
Actually in Qt documentation it's written in the description of zoomReset() function that
Resets the series domains to what they were before any zoom method was called.
Which means that the series of operation should be 1) Zoom 2) Scroll right/left/up/down.
If you perform above sequence of operation then zoomReset() will work.
It seems that it is correct also if you have performed scroll operation first then it is also obvious that you want to analyze in scrolled Area only so zoomReset() will just then resets zooming only...
Don't understand your question. Assuming you are now compiling 64-bit (right? and that's perhaps unlike in 2012), then sizeof(qint64) == sizeof(int). It will only resize to the value specified, even if the variable could hold a huge number. If the length is only 88K that's what it will resize to, regardless of the type of the variable.
Yes, but invokeMethod() is on QMetaObject, and that's what I refer to as the "magic" of the old ... (look up a string in a table of functions, rather than using language constructs). You have to pass a test before being allowed to use that, and your programming license will be revoked if you don't know what you are doing and get it wrong... :)
Apart from @Christian-Ehrlicher's observation about tool for detecting memory consumption.
I was looking at this recently. What exactly do you mean by "the pointer is deleted"? If you use the usual deleteLater(), memory does not freed until execution returns to the top-level Qt event loop, not before. Or, are you using delete? Even then I wouldn't rely on it being returned to the OS for a one-off. Have you tested this against creating hundreds/thousands of instances of the widget?
And if you in the process,
completely delete ui_QtGuiApplication1.h
and rebuild build all ?
It sounds like some code left overs.
"This is because the code doesn't test if the QTableWidgetItem * "
Why would it be NULL ?
If you delete from the UI (visually) that code should no longer be there.