File bluez.cpp

A lot of Exception checking is going on, but not a lot of exception handling...

A few QDBusPendingCall::waitForFinished() are used as temp shortcuts. The code ought to use only asyncronous calls though. This may also pose a threat to the assumption that only one signal is being processed at any time (the consequences of using waitForFinished() is not clear in the documentation)!

Support for BlueZ v.5. should be implemented at some point.

Class fsdc::Core::DataAvailable

Fixme: Document me

Class fsdc::Core::RegisterDataType

Fixme: Document me

Class fsdc::Core::UnRegisterDataType

Fixme: Document me

Class FSYS::MsgAddrGenerator< T >

Make a base class of this to handle the MsgAddr

Class PAL::BluetoothModule

Revisit documentation for instructions on starting and terminating the module using the module launcher

Member PAL::BluetoothModule::BluetoothModule ()

Revisit documentation for instructions on starting and terminating the module using the module launcher

Member PAL::PersonalHealthDeviceConnector::disconnectIndication (std::shared_ptr< VirtualPHD > device, errortype error=0) noexcept=0

Fix doc when the actual errortype has been chosen...

Class PAL::PHDBluetoothDevice

Describe how the HDP standard maps to this interface

Class PAL::PHDUSBConnector

This specialization must be defined when the first USB device is integrated in this framework.

Class PAL::PHDUSBDevice

This specialization must be defined when the first USB device is integrated in this framework.

Class PAL::PHDZigBeeConnector

This specialization must be defined when the first ZigBee device is integrated in this framework.

Class PAL::PHDZigBeeDevice

This specialization must be defined when the first ZigBee device is integrated in this framework.

File personalhealthdevice.cpp

The following paragraph should probably be moved somewhere else.