On Wed, Jan 17, 2018 at 9:27 AM, Robert Tiemann <rtie(a)gmx.de> wrote:
> If we will go ahead, I think that maybe it's worth to
> PropertyChanged signal to notify Security property has changed when
> wps_adversing is added/removed.
This would be helpful indeed. My current client code constantly scans
for WLANs and reads out all data of all services on _any_ change
reported. Not very efficient, but it turned out to be the most
reliable way to keep up with changes.
I would say that avoid doing that is exactly the reason why signals are used :)
Alternatively, wps_advertising could be turned into a property in
own right, outside of Security in case Security is not supposed to
change. I just thought it would make sense to put it into Security.
I would rather add it into the Security property. Let's see what
Daniel thinks about it.
I guess to generate the PropertyChanged signal, a function similar
strength_changed() would be needed which calls
Shall I prepare two patches (one for the signal, one for the docs)?
Yes, please divide it into two patches.