Ok, I'll give it a go. But I'm warning you windows, this better all be worth it!
I just didnt want to get stuck down with using all proprietary windows stuff. I have never used Qt with VS before. Suppose its about time I tried!
Ok, I'll give it a go. But I'm warning you windows, this better all be worth it!
I just didnt want to get stuck down with using all proprietary windows stuff. I have never used Qt with VS before. Suppose its about time I tried!
Ok Ive had enough.
I spent 3 hours downloading, configuring and nmakeing QT then I have spent the next 5 hours trying to get the WINAPI code working. I havent. So I give up. I dont like using VS Express 2008 anyway. Its too big, cumbersome, and it feels like the Qt integration has been bodged.
Back to QDevelop and no interesting CPU information. Hopefully Qt will add it in the future.
Cheers,
Phil
It shouldn't be that difficult. Download Qt source, configure, nmake, wait. Then use nmake to compile your projects (either with VS or from the command line). If the headers you need aren't in VS, then you might need the full platform SDK.
I generally prefer mingw+qdevelop as well, but when you need windows stuff beyond the basics it causes more problems than it solves.
I wasnt difficult, just complicated. There are too many hoops to jump through to get thing to do what you want. But the code itself was utterly rediculous. It should be as easy as calling a function. But its not.
The program complied fine, and it was working to an extent, but the person who wrote that code took a stats reading, sleep for 2 seconds, took another stats reading then took the two results away from each other. I tried to change it so it didnt have to sleep, but it didnt work. So I gave up.
This was all for a bit of eye candy anyway. Not essential.
Bookmarks