On 01/17/2018 08:54 AM, Jose Blanquicet wrote:
Hi Robert, Daniel,
If we will go ahead, I think that maybe it's worth to generate a
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.
Alternatively, wps_advertising could be turned into a property in its
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.
Furthermore, Service API documentation should be updated with the
possible value for Security property.
I guess to generate the PropertyChanged signal, a function similar to
strength_changed() would be needed which calls
Shall I prepare two patches (one for the signal, one for the docs)?