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
Attachments: