StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9964855
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-04-01T13:46:24.960
FavoriteCount
0
LastActivityDate
2012-04-01T13:46:24.960
LastEditDate
LastEditorUserId
0
OwnerUserId
1157224
ParentId
9964431
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Inheritance is one of the greatest things of OOP, if used correctly. A "subclass", in all good OO designs, has to obey a simple rule: IS the child a KIND OF parent? That is usually called, in OOP literature, a "is a" relationship. And more important: the child has always to do two things: specialize a generic behavior, or extend the functionality of the father. I consider it a code smell when a subclass does neither. That said, your decision has nothing to do with Qt, or with what's programatically better or worse. It should make sense. An example: If you had a QLabel that had to show the score of a game, and only that, it could be a good idea to do something like <pre><code>class MyScoreBoard : public QLabel { private: int scoreP1; int scoreP2; Game *_g; public: MyScoreBoard(QWidget *parent = 0) : QLabel(parent) { scoreP1 = 0; scoreP2 = 0; connect(_g, SIGNAL(scoreChanged(int,int)), this, SLOT(updateScore(int,int))); } public slot: updateScore(int a, int b) { scoreP1 = a; scoreP2 = b; this->setText(QString::number(scoreP1) + "x" + QString::number(scoreP2)); }; }; </code></pre> On the other hand, if your scoreboard had some lights on top of it, that should blink whenever the score had changed, if it had one label for each player, that had to change its color depending on the score, then it would be better to create a ScoreBoard class that HAD two labels, HAD two lights, and then implement the intended behavior. Bottom line is: inherit if it makes sense on your design <a href="http://en.wikipedia.org/wiki/Yo-yo_problem" rel="nofollow">Wikipedia has a good small article about an anti-pattern that appears when inheritance is used without care.</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQt - proper design of application code
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USCastilho
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQt - proper design of application code
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.