StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12222972
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-31T22:00:39.827
FavoriteCount
0
LastActivityDate
2012-08-31T22:09:00.320
LastEditDate
2012-08-31T22:09:00.320
LastEditorUserId
1631883
OwnerUserId
1631883
ParentId
11400466
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
First of all, although signals\slots are a powerful and awesome feature of Qt I would never use them in my rendering routines because of the added overhead and render order problems; especially the latter. Besides, it's not necessary to do it the way you propose. Thus, your idea of scattering the rendering routines all over your project is a very bad idea in my opinion. What I do in my own project is the following: My derived <code>QGLWidget</code> owns a <code>Renderer</code> class that's implemented as a Singleton. It contains all of the OpenGl calls in a few functions. I've created a system where everything that's drawable derives from the same base class. When I want to render, I build a render queue which I implemented as a <code>priority_queue</code> with custom sort function. When It's time for rendering a frame I just keep poppin' and rendering until the queue is empty. Doing this with an event driven render system, while maintaining correct render order would probably drive you insane. For completeness, my (simplified) QGLWidget definition: <pre><code>#include <QtOpenGL/QGLWidget> #include "global.h" #include "renderer.h" /** * Derivation of QGLWidget. */ class Engine : public QGLWidget { Q_OBJECT private: Renderer* renderer; private slots: void renderTimeout(); // my render-loop is timer based void onTap(QMouseEvent* qme); void onMove(QMouseEvent* qme); protected: void initializeGL(); void resizeGL(int w, int h); /* for debugging I use QPainter for drawing overlays, * so I can't use PaintGL */ void paintEvent(QPaintEvent *event); void mousePressEvent(QMouseEvent* qme); void mouseMoveEvent(QMouseEvent* qme); public: Engine( QWidget* parent = 0 ); ~Engine(); signals: void tapOccurred(QMouseEvent* qme); void moveOccurred(QMouseEvent* qme); }; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTrying to access QGLWidget from entire application
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpauluss86
UserOwnerUserId
1. USpauluss86
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POTrying to access QGLWidget from entire application
 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
 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.