Explore >> Select a destination
|
You are here 
|
lowleveldesign.wordpress.com | ||
| | | | |
blog.willportnoy.com
|
|
| | | | | For a project at work, I implemented the Paxos distributed consensus algorithm. When I first started the project, I needed a mechanism fo... | |
| | | | |
blog.willportnoy.com
|
|
| | | | | There are times when you would like to use a native DLL with ASP.NET, and the ASP.NET compilation process fails with a BadImageFormatExcepti... | |
| | | | |
sergioprado.blog
|
|
| | | | | In this article, we will learn how to debug the Linux kernel on an embedded Linux system with GDB. | |
| | | | |
dvratil.cz
|
|
| | | Thank you to everyone who reported issues and contributed to QCoro. Your help is much appreciated! Support for awaiting Qt signals with QPrivateSignal Qt has a feature where signals can be made "private" (in the sense that only class that defines the signal can emit it) by appending QPrivateSignal argument to the signal method: class MyObject : public QObject { Q_OBJECT ... Q_SIGNALS: void error(int code, const QString &message, QPrivateSignal); }; QPrivateSignal is a type that is defined inside the Q_OBJECT macro, so it's private and as such only MyObject class can emit the signal, since only MyObject can instantiate QPrivateSignal: | ||
