   (ab)using signals/slots to compensate pour pointer handling?
  Well, since I am pretty new to making "bigger" projects in c++,I am currently fiddling with QT to make a "flexible" GUI, where one can rearrangewidgets in the way they like.I couldn't use the standard mainwindow-layout, because we have no "central" thingy, which is required when using a centralwidget+toolbars+toolwindows and whatnot.My fiddling resulted in (some) pointer issues.Currently I am on the way to "abuse?!" signals and slots for keepingpointers consistent. Meaning:object-construction -> bind delete-signal to here.pointer-to-object is passed to some other class -> bind delete-signal there.object gets destroyed -> anyone gets notified.As long as I don't have to put 1000 functions in (which could happen if it continues this way :P) it should be ok, should it?I guess its due to my lack of good planning, since (the gui alone) has grown bigger than I thought. Wishes arised, which made me break my "competence-system".Is this just a matter of experience?How do you manage your class-design, and how do you break it if it's needed?   
  It sounds like you've almost discovered smart pointers, in particular weak pointers. If you have to use C++ for something, the use of smart pointers can save time while making your code more robust and efficient.   ;  I'll remember next time. Promised.   