[mythtv] Re: Ticket #341: Music database update does not reread metadata

[Eskil Heyn Olsen]

On Thu, 2005-10-27 at 03:51 +0000, MythTV wrote:

>  Yep, there are a lot of bad deletes of QObjects. Technically this is only
>  a problem if signals or slots are in use. But, some normal QObject calls
>  use signals in the background, like timers and the like.

as to not continue the thread in the bug...

I'm new to the whole QObject model, was in the gnome world for a long
time and blablabla = some questions, if you don't mind. Mostly just
because I'm curious, so don't feel obliged to answer.

I was under the impression that every object in the QObject hierachy
should declare the Q_OBJECT macro. However, most of the MythWidget
classes don't. What does this do ?

I understand how deleting an object can cause a timer that triggers
later to sigsegv, if it refers to the deleted object. But why would
deleteLater cause the subsequent havoc ? What I saw in the flurry of
patches was;
	MythBusyDialog *b = new MythBusyDialog ();
	...
	b->deleteLater ();
	b = NULL;

	MythProgressDialog *p = new MythProgressDialog ();
	...
	delete p; // bang, program dies in the ~MythProgressDialoag.

This, I just don't get.

eskil
---