[Interest] Heavily Commented Example: Simple Single Frontend with Two Backends

Alan Ezust alan.ezust at gmail.com
Tue Oct 23 17:52:05 CEST 2012

Comment from one of the files in that .zip file:

>When we call this->setLayout(m_Layout), 'this' becomes the parent of
> m_Layout and all child objects (everything we add to the layout becomes a
> child of m_Layout), and deletes it (and all children) for us when 'this'
is destroyed

Not exactly true. When you add a widget to a layout, it becomes a sibling
object of that layout.
If you add a layout to a layout, it becomes a child of that layout.

On Sun, Oct 21, 2012 at 12:16 AM, d3fault <d3faultdotxbe at gmail.com> wrote:

> I created this for two reasons:
> 1) To be a good starting/reference point for Qt beginners. I'm trying
> to combat the misinformation on how to use QThreads that the outdated
> docs have embedded into so many brains. I hope this will jumping out
> somewhere on the qt-project.org/docs/ so that it can serve as a basic
> "Intro to Qt" (for relatively experienced programmers).
> 2) To get feedback and as a sanity check of sorts. HAY EXPERTS, AM I
> Please feel free to contribute in any way possible, whether it's
> discussion on the proper use of Qt or if you're just improving
> grammar/understandability of the comments.
> I do feel it is relatively complete, however.
> I have attached it, but here's an external link as well:
> http://bayfiles.com/file/oC1L/kQcSQW/SimpleSingleFrontEndWithTwoBackEndsExample.zip
> d3fault
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20121023/78122f67/attachment.html>

More information about the Interest mailing list