Brainstorm

' C++ GUI Programming with Qt4 ' is very easy, given you have enough knowledge in c++. Don't understand what you find difficult.

Well, I would like to join the dev team. However, I have to find time. I will look for its IRC channel Thanks all :)

Well, OK, then I forget that one in my file format plans :) Thanks anyway!

Glad you posted this. I was also as curious as you are. Will check out the suggestions. thanks!

Hmmm, one way would be to provide a custom delegate (see [[Doc:QStyledItemDelegate]]) that knows about flashing.

[quote author="hisoft" date="1314093113"]Hi, Thanks for replying. I didn't know that it's not Qt related as i hasn't any idea how to do it. I just started reading the articles you forwarded me to, and it seems to be what i'm looking for ![/quote] No problem, sometimes it's not clear where to post in the first place. We move stuff to the right forum then, nothing you must be worried about too much. If you've come to a solution, feel free to report back here. We'll be glad to hear that we could be of help.

Yeah, I'll look into it once I decide to use such logging, thanks for the input.

[quote author="qt-newbie" date="1313106592"]Loladiro, Thanks. I got the button text labels via the QAbstractButton class. Please explain where "queryInterface(nr)" is defined. I am a bit confused. Do I need to write a class/method for this ? Is it a wrapper ? Thanks, Qt-Newbie[/quote] Since I have no idea what kind of interface you have I just put it there to indicate where you have to query your interface.

And thus, the Muffincycle Party was born with the nomination of it's first candidate. :-)

Two years ago I asked myself the same question. My solution: getting the QtCreator source code and study it. QtCreator is exactly the kind of application you descibe in your post. It is very well designed and you can learn a lot from it - especially how to make a modular, plugin based application. Another good example for such a plugin based framework is the "Generic Component Framework":http://www.vcreatelogic.com/products/gcf/. You can use this framework out of the box without the need to design your own. Another great source for learning is the "Qtilities":http://www.qtilities.org/ library.

code works if I comment call of DrawThemeTextEx It draws may be need to set clipping before call it? OMG! @typedef HRESULT (*PDrawThemeTextEx)( HTHEME hTheme, HDC hdc, int iPartId, int iStateId, LPCWSTR pszText, int iCharCount, DWORD dwFlags, LPRECT pRect, const DTTOPTS *pOptions );@ I forget typedef WINAPI Should be @HRESULT (WINAPI *PDrawThemeTextEx)( HTHEME hTheme, HDC hdc, int iPartId, int iStateId, LPCWSTR pszText, int iCharCount, DWORD dwFlags, LPRECT pRect, const DTTOPTS *pOptions );@ All works!!! Thanks all PS. never ever copy-paste function declaration from MSDN!!!

I moved this thread to the brainstorm forum, as it's only marginally Qt related.

[quote author="loladiro" date="1309941231"]Or something like this @SELECT a FROM (SELECT a, COUNT(DISTINCT b) as c a_b WHERE b IN(1,4) GROUP BY a HAVING c=2)@[/quote] Good, that's what I want.

Thanks Andre. I think I know how I'll go about and design this.

If one is trying a use a class and looks at the documentation, it is quite obvious. I also understand that Qt documentation provides a list of "obsolete classes":http://doc.qt.nokia.com/4.7/obsoleteclasses.html each version. But unless you're constantly looking to keep the code up-to-date, you might not keep track of it. I usually compile the new version.. fire up assistant and continue working on the client's requirements. Maybe, it would be good to make that page more prominent and have a more in-your-face-visibility web page for it here on devnet. But then again, i don't see too many classes on the list. Anyhoo...

Damnit, curiosity killed the cat again....

Of course. I can post a screenshot as soon as I have something interesting.

I think maintainability is more important than you avoiding an if statement. It is hard to understand what piece of data is where if you use an array to store them. That may lead to bugs in Qt in the future. So please, don't. Adding a convenience function that implements operator is fine by me, but the implementation would basically look like FrankZ's proposal. I am not sure if adding a size to a point should yield another point, but perhaps it should. That would be easy to implement. You might want to supply a merge request containing the patch and a use case and/or other argumentation why this is needed.