I would avoid assert for thoses cases. They prevent a race condition, it may just be normal to trigger them. Using an assert will kill the client. Dynamic cast will just make sure the call have not been already deleted somewhere else in the code.
This is not ideal, but signals order is very hard to control. But as I said, please use 1.1.0. SFLPhone KDE v1.0.2 have never been released as stable or supported in the first place. 1.0.0 work well and 1.1.0 is fully supported again, the first release to be since 0.9.6. ----- Original Message ----- From: "Vipul Mahajan" <[email protected]> To: "Emmanuel Lepage" <[email protected]> Cc: [email protected] Sent: Monday, May 28, 2012 11:04:19 AM Subject: Re: [SFLphone] Problems with SFLPhone 1.0.2 KDE client Hi, I was just wondering whether the following conditional checks should be reversed e.g. '!= 0'. Is it correct? Q_ASSERT_X(confItem->childCount() == 0, "add conference","Conference created, but without any participants"); Q_ASSERT_X(SFLPhone::model()->getIndex(conf)->childCount() == 0,"changing conference","A conference can't have no participants"); ___________________________________ Thanks & Regards Vipul Mahajan _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
