jeena/telldus
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Tried to clarify the fallback mechanism used in tdMethods()

Browse source
This commit is contained in:
Micke Prag 2012-01-23 11:12:46 +01:00
parent a26244fa95
commit fec44a8e77
1 changed files with 6 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/01-telldus-core.dox
View file

@ -94,8 +94,12 @@
* } * }
* \endcode * \endcode
* *
* By supplying the methods the application supports, the library can be backwards * By supplying the methods your application supports, the library can return
* compatible. Let's say that the client application only supports turning on and * customized methods for your application, even if your application doesn't
* support the same methods as the device accepts. One example is if your
* application only supports ON and OFF, you can control a device that needs UP
* and DOWN anyway by using just ON and OFF.
* Let's say that the client application only supports turning on and
* off. The call to query a device for it's methods should be: * off. The call to query a device for it's methods should be:
* \code * \code
* int methods = tdMethods( id, TELLSTICK_TURNON | TELLSTICK_TURNOFF ); * int methods = tdMethods( id, TELLSTICK_TURNON | TELLSTICK_TURNOFF );