-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2018/10/11 02:34 PM, deloptes wrote: > Michele Calgaro wrote: > >> Hi Emanoil, can you be a bit more clear on how to reproduce this? I am not sure I have understood. Cheers >> Michele > > Hi Michele, I was wondering if someone has hit this issue. It comes from dbus-1-tqt, but does not hurt the > application. > > I think the problem is in the nature of the DBus call. You probably recall that I am playing recently with > dbus-1-tqt and auto generated code (for bluetooth). Unfortunately dbusxml2qt3 does not generate the asynchronous > methods out of the introspectable xml. I think this is the problem as the nature of the call in question is > logically asynchronous. > > It is long to explain how to reproduce it, but here is a brief summary. > > 1. generate interface for agent mkdir agent cd agent rm -f ./*.h ./*.cpp && /usr/bin/dbusxml2qt3 > org.tdebluez.agent.xml 1.1 you need to fix #include agent1.h => agent1interface.h 2. implement (the example from > the TDE wiki) 3. implement dialog that is started with exec() and is called in RequestConfirmation 4. call pair > with device (from dbus or code) > > => when dialog window pops up - it blocks and those messages come with thousands until you press the button. > > This makes me think an async method would be more appropriate here. I will try in the next days and report back. > Perhaps we can extend dbusxml2qt3 to create async calls as well. > > Let me know what you think, if you have some ideas. > > thanks and regards > > Hi Emanoil, give me some time to look at this with more attention in the next week or two. This week I won't be able to give it much time. Cheers Michele -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEjhl1z5vbYB3YbFTiKnW3yore1c8FAlu/UpYACgkQKnW3yore 1c/4lxAAhX0YGPMV3GJ7O38J+cE6iboXEFvzTtsm8cUwoKV/jAxo1chcIeSQRfP0 fJLxyl6DtjthnlwKRM1lhzwnaBq2Meq2Qb4bPFmfA8SGc0qySmxE7mby9FU8B9FF 4Kzj/WfyGpL3/+BGzvMkGXBWII/gyxVMsL+O6PKuLTMcoHCSBYMaUMLGhfpooZBs qzIqCKxq5oK0NP8+oFQAl3sPr7aEyoAUeEzLwKeD8zgr/EJZ0D0NCbADJMvOy8A5 mtV4Phk5+56QCA2mgqygMQX0hnLqm58XJjUATzplYM7eLQWj1+Hme8hE3k0Sr+KR pL1gf0uPCO8DL8Bn4s8Fu6EjpTlU/M6K1zXdTx46hMR2sLpySFN4m343gfFQTzU5 LntO0/M7dmLeNbjMxjNtaem9mSBrT9b3O2xzJKkRCzE/CvDUZOt3DN2n079zGt1k Cn4enGo4TsVKtYgB34ey5v1px8muwVUcW4MEkKN2cDiu5jvNZBi80woOGWq0UboG ib25BE4Hr23ufX4XM+b+dHIbdlTkI1SFGrm+xkXSKUx1wiZ2QRHSjfXuLpWvjm1/ mgqwkyA9r48XLL8QT9Bgrf1uSa1IQxTtNkMCtWMVogRPli5VmPp4Y/mXRqi0wb52 lQmNcyItLP+UqOZVPPi/F4issVEVWv19jqiocE2VY7AFTcuAtBM= =TtFO -----END PGP SIGNATURE----- --------------------------------------------------------------------- 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
