I'm not sure why I'm replying, as the attitude of the inquirer is decidedly hostile, but here goes:

Quote Originally Posted by VireX View Post
I am saying that I cannot use qmake + make to build my project, make gives me errors because of qmakes inability to make correct makefiles.
What QMAKESPEC are you using? This is crucial. Let me repeat, this is crucial.

It is an unfortunately fact of development that make was never standardized. Don't blame Trolltech for this. A makefile meant for MS Visual Studio will not work with GNU Make (MinGW, etc). So go check what your QMAKESPEC is. If DevC++ uses GNU Make, then you need to use the win32-g++ QMAKESPEC.

Quote Originally Posted by VireX View Post
Your points:
* I'd prefer ugly macros that I don't have to deal with than pretty connect functions that require me to use moc every time I need to change slots/signals. Is it really impossible to make it so you don't need moc?
MOC is easy. Get your qmake working and you still stop having problems with moc. Most people never ever touch moc. In fact, I don't remember the last time I ran it manually.

Actually, you don't need moc. If you hate it that much, then don't use it. But that means you have to write the backend dispatch code yourself using QMetaObject. It's like using MFC without the the Visual Studio wizards. It's certainly possible, but very few people are inclined to do so.

Quote Originally Posted by VireX View Post
You have a button, your library should automatically assign ids to all objects, and then you can have a connect function, just like the qt one, except that when someone uses a custom function, send the function and the class it involves, and then connect the on click WM_COMMAND to the function that was given by connect. It might be hard, but it should be able to be done.
Qt gives you a much more flexible system. You can connect multiple signals to one slot. One signal to multiple slots. Or multiple signals to multiple slots. You can even connect a signal to a signal! It allows you to pass information in a natural way, as custom parameters to your slot. It allows you connect and disconnect objects dynamically at runtime.

No other toolkit offers this amount of flexibility at this cheap of a price. So get your qmake working, and start seeing it for yourself.