@VRonin I don't doubt that Visual Studio can do this, my poins are
qmake doesn't have native way to set source-specific flags, you need to create your own custom target with all gory details of building C++ file, so it's much easier to move it into library
I don't know if mixing EH flags in the same binary is reliable with MSVC
It's an application that runs on a big screen that people will use standing up. So they will be using touch rather than a keyboard.
The reason for Windows 7 is that the application will need to attach to hardware, D2K-DASK http://www.adlinktech.com/PD/web/PD_detail.php?pid=350. The hardware drivers are only guaranteed for Windows 7 and 8. Its possible it might work on Windows 10 anyway but it's not clear.
There's no need for any global objects all the more if you only have one active connection for your application but it's also valid if you are managing multiple connections. The QSqlDatabase class already provides everything you need.
Like written in the documentation, if you are only using one connection, don't give it a name, it will become the default connection and all the SQL related classes will use it by default.
If you have several connections, it's easy to retrieve the one you are interested in by using QSqlDatabase::database.
On a side note, you should properly test the outcome of your open call. Right now it could be failing and you don't care about that possibility.
Put a QSortFilterProxy model in-between. then save from the proxy instead of the main model.
connect(currentTableHeader, SIGNAL(sectionClicked(int)), this, SLOT(on_sectionClicked(int))); and void mainWidget::on_sectionClicked(int index) are useless. this is the default behaviour of QTableView, you don't have to implement it manually
I sincerely want to thank you for your help! This project took six-months and your assistance was crucial in getting over the goal line in the final week. If I missed that hard deadline my six-month contract-to-hire would have been terminated. Partly because of your assistance I made it work and was hired full-time permanent! We shipped Version 1.0 and two weeks later I delivered a significant V1.1 follow up!.
I momentarily had it setup as a (static?)linked library but backtracked to direct #includes from the /common/ folder, mainly because I understood it better. I intend to switch again to the library method because of compile times as you suggested. I was also scared off by an article suggesting I would need to add C++ #EXTERN statements, etc. to create a public interface for the library. Is that true, or can the .pro/.pri files define that folder as a library with NO changes to the C++?
I still have to migrate *.qml files to the /common/ but I assume it's basically the same pattern as the C++. I haven't replied because I thought I had more questions but the project has been moving too rapidly.
How do you know that A, B and C are equal to 0? If they are, then your program will give error when you click on "calculate" - "Division by zero".
Could you put some debug statements in your code?
qDebug() << "A: " << A << "\tB: " << B << "\tC: " << C;
delta = ((B * B) - (4 * (A * C)));
@joeQ As it turns out, I just tried the opposite. I had one newed Message Box for everything. In the place that had the funny location, I made a separate newed Message Box and it ended up in the correct place - the middle of its parent.
@diredko Why passing it once using a normal function (Q_INVOKABLE) would hurt performance in your opinion? It would certainly be more efficient to have a big list in QML than use a function again and again, and such a list isn't big for modern hardware (couple of hundreds of KBytes maybe). If you can afford to have that list in C++ you should be able to afford to have it in QML, too.
I think the biggest performance obstacle is that the system isn't real-time, QML may do garbage collection and animation isn't fluent. I recommend just testing with the most easy solution in the lowest end hardware it will be run on and deciding after that if it's enough.
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.