One more thing: this should have been one of my first things I tried, but I ran the debugger and got the following message - "The inferior stopped because it received a signal from the operating system
Signal name: SIGSEGV
Signal meaning: Segmentation fault",
and it pointed directly at my destructor for DataPiece, which simply calls "delete this" (even though I never actually call the destructor in my code, it must be an implicit call).
After briefly looking up this error, I primitively discovered that this generally occurs when attempting to illegally access a register in memory. So then I looked at how I initialized my DataPiece, realizing that I actually wasn't calling any of my constructors. So, I passed it a parameter 'this' to act as the QObject * parent, but this still didn't resolve my SIGSEGV issue.
You have to use the correct moc to your headers. When you install Qt you must also install the devel tools for this specific Qt versions. And you should fix your buildsystem to call moc. Those moc files do no belong to the sources.
.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.
The export (or lack thereof) definitely was the problem. Once I got in this morning and cleaned up by code a little and rebuilt everything the export is now working fine. I must have had an old build of something that wasn't getting cleaned.
You don't have to mix anything.
What you use in your enum are hexadecimal values not binary.
That means (left side hex, right side binary): 0x0 == 0, 0x1 == 1, 0x10 == 10000, 0x100 == 100000000!
I guess what you actually want is what Chris Kawa said: 0x01 == 1, 0x02 == 10, 0x04 == 100, 0x08 == 1000, 0x10 == 10000
You did a complete rebuild as well?
The run of qmake does not create an error code, but it does not introduce a moc statement into makefile.
I guess you are using a shadow for compiling. Delete the whole shadow folder, rerun qmake once again and rebuild.
If you think it imay be a bug related to Qt 5.5 you can check on JIRA.
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.