@@ -99,15 +99,17 @@ This can be changed to use passkey authentication or numeric comparison. See [Se
9999The ` NimBLEAdvertisedDeviceCallbacks::onResult() ` method now receives a pointer to the
100100` NimBLEAdvertisedDevice ` object instead of a copy.
101101
102- ` NimBLEClient::connect() ` now takes an extra parameter to indicate if the client should download the services
103- database from the peripheral, default value is true.
104-
102+ ` NimBLEClient::connect() ` Has had it's parameters altered.
105103Defined as:
104+ > NimBLEClient::connect(bool refreshServices = true);
106105> NimBLEClient::connect(NimBLEAdvertisedDevice\* device, bool refreshServices = true);
107- > NimBLEClient::connect(NimBLEAddress address, uint8_t type = BLE_ADDR_PUBLIC, bool refreshServices = true);
106+ > NimBLEClient::connect(NimBLEAddress address, bool refreshServices = true);
107+ <br/>
108108
109- If set to false the client will use the services database it retrieved from the peripheral last time it connected.
110- This allows for faster connections and power saving if the devices just dropped connection and want to reconnect.
109+ The type parameter has been removed and a new bool parameter has been added to indicate if the client should
110+ delete the attribute database previously retrieved (if applicable) for the peripheral, default value is true.
111+ If set to false the client will use the attribute database it retrieved from the peripheral when previously connected.
112+ This allows for faster connections and power saving if the devices dropped connection and are reconnecting.
111113<br />
112114
113115> NimBLERemoteCharacteristic::writeValue();
@@ -117,6 +119,7 @@ Now return true or false to indicate success or failure so you can choose to dis
117119<br />
118120
119121> NimBLERemoteCharacteristic::registerForNotify();
122+
120123Is now ** deprecated** .
121124> NimBLERemoteCharacteristic::subscribe()
122125> NimBLERemoteCharacteristic::unsubscribe()
@@ -129,7 +132,7 @@ Are the new methods added to replace it.
129132> NimBLERemoteCharacteristic::readUInt32()
130133> NimBLERemoteCharacteristic::readFloat()
131134
132- Are ** deprecated** and NimBLERemoteCharacteristic::readValue(time_t\* , bool) template added to replace them.
135+ Are ** deprecated** and NimBLERemoteCharacteristic::readValue<type \> (time_t\* , bool) template added to replace them.
133136<br />
134137
135138> NimBLERemoteService::getCharacteristicsByHandle()
@@ -152,8 +155,9 @@ uint8_t *val = (uint8_t*)pChr->readValue().data();
152155> NimBLERemoteService::getCharacteristics(bool refresh = false)
153156
154157These methods now take an optional (bool) parameter and return a pointer to ` std::vector ` instead of ` std::map ` .
155- If passed true it will clear the respective vector and retrieve all the respective attributes from the peripheral.
156- If false(default) it will return the respective vector with the currently stored attributes.
158+ If passed true it will clear the respective vector and retrieve ** all** the respective attributes from the peripheral.
159+ If false(default) it will return the respective vector with the currently stored attributes.
160+ <br />
157161
158162** Removed:** the automatic discovery of all peripheral attributes as they consumed time and resources for data
159163the user may not be interested in.
@@ -177,6 +181,17 @@ The client will automatically initiate security when the peripheral responds tha
177181The default configuration will use "just-works" pairing with no bonding, if you wish to enable bonding see below.
178182<br />
179183
184+ # General Differences
185+ ` NimBLEAddress() ` When constructing an address the constructor now takes an optional ` uint8_t type ` paramameter
186+ to specify the address type. Default is (0) Public static address.
187+
188+ Defined as:
189+ > NimBLEAddress(ble_addr_t address);
190+ > NimBLEAddress(uint8_t address[ 6] , uint8_t type = BLE_ADDR_PUBLIC);
191+ > NimBLEAddress(const std::string &stringAddress, uint8_t type = BLE_ADDR_PUBLIC);
192+ > NimBLEAddress(const uint64_t &address, uint8_t type = BLE_ADDR_PUBLIC);
193+ <br/>
194+
180195# Security Differences
181196Security callback functions are now incorporated in the NimBLEServerCallbacks / NimBLEClientCallbacks classes.
182197However backward compatibility with the original ` BLESecurity ` class is retained to minimize app code changes.
0 commit comments