deloptes wrote: > No problem with me Michele, I appreciate the support at any time. > I will just try with an async call in the context if possible - need to > investigate. I looked yesterday, so following is happening: 1. App is sending async Pair request to the device 2. Device responds and org.bluez.Agent1.RequestConfirmation is called 3. RequestConfirmation runs a dialog (Ok|Cancel) and the worning is displayed 1000s of times until user confirms/rejects Note: the class implementing RequestConfirmation is not (T)Q_OBJECT class but creates and runs the dialog. (not sure if this is related) It might be that I also misunderstand the way it has to be implemented, but it might be that there is a reason for this wawrning in dbus-1-tqt Last but not least, it is just a worning and code works as expected. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-devel-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
