Re: Does -peripheral:didWriteValueForCharacteristic:error: reflect the new value?
Re: Does -peripheral:didWriteValueForCharacteristic:error: reflect the new value?
- Subject: Re: Does -peripheral:didWriteValueForCharacteristic:error: reflect the new value?
- From: Etan Kissling <email@hidden>
- Date: Wed, 12 Jun 2013 07:48:50 +0000
- Thread-topic: Does -peripheral:didWriteValueForCharacteristic:error: reflect the new value?
Rick,
have to issue another readValue call, as this is profile-specific. What you write
into a characteristics is not linked to what is returned when you read it.
There are also write-only characteristics (control points) where
reading out a value wouldn't make sense at all.
It's just a convenience for many characteristics like "Device Name", that the value
that was previously written is stored for later read-out.
Etan
On 11.06.2013, at 08:40, Rick Mann <email@hidden>
wrote:
> In the callback after writing a characteristic's value, does the characteristic.value reflect the newly-written value? Or do I have to issue another -readValueForCharacteristic: call?
>
> --
> Rick
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Bluetooth-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden