All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yunchuan Geng <yunchuan.geng@nomovok.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: property changes emited but not captured, why?::
Date: Mon, 4 Apr 2016 14:38:47 +0300	[thread overview]
Message-ID: <57025247.3080709@nomovok.com> (raw)

Hi,

I am testing map-client python script from bluez-5.30. Everything works 
fine, except that I found I can not capture the properties change signal,
which I confirmed from log did been emitted from parse_subject function 
in obexd/client/map.c

In order to check if the signal is captured in python script or not, I 
have patched the script like this. But have not catch any signal the 
parse_subject
function has emitted.

Could anyone tell me why and how to correctly capture property changes 
emitted by g_dbus_emit_property_changed function.


Yunchuan

=====Patch=====
diff --git a/test/map-client b/test/map-client
index b9695da..634b91a 100755
--- a/test/map-client
+++ b/test/map-client
@@ -118,6 +119,9 @@ class MapClient:
                 mainloop.quit()

         def properties_changed(self, interface, properties, 
invalidated, path):
+                print(properties)
+                print(interface)
+                print(path)
                 req = self.props.get(path)
                 if req == None:
                         return


             reply	other threads:[~2016-04-04 11:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04 11:38 Yunchuan Geng [this message]
2016-04-04 13:04 ` property changes emited but not captured, why?:: Luiz Augusto von Dentz
2016-04-04 18:58   ` Yunchuan Geng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57025247.3080709@nomovok.com \
    --to=yunchuan.geng@nomovok.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.