archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <>
To: Andrei Datcu <>
Subject: Re: Calling Service::Remove will not raise the Service::PropertyChanged event
Date: Fri, 2 Jul 2021 09:25:40 +0200	[thread overview]
Message-ID: <20210702072540.h2anfir7n76nnu5h@beryllium.lan> (raw)
In-Reply-To: <>

Hi Andrei,

On Tue, Jun 22, 2021 at 09:15:24PM +0300, Andrei Datcu wrote:
> I'm having a wifi service with:
> State == "idle"
> Error == "invalid-key"
> Calling Service::Remove() will correctly reset the "Error" property.
> There will be no Service::PropertyChanged signal emitted however. Is
> this a bug or is this technically not considered a property change
> since the property is now missing all together from the property set?

Good question. I tend to say, the reason why no PropertyChanged is
issued is that the service itself is removed and not just a
property. Given that you call 'Remove' and get a reply message which
says, it the request was either successful or not should be
enough. Also, the D-Bus service object should be removed then and
this should give another signal source.


      reply	other threads:[~2021-07-02  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 18:15 Calling Service::Remove will not raise the Service::PropertyChanged event Andrei Datcu
2021-07-02  7:25 ` Daniel Wagner [this message]

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:

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

  git send-email \
    --in-reply-to=20210702072540.h2anfir7n76nnu5h@beryllium.lan \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).