Changeset fec44a

Timestamp:

01/23/12 11:12:46 (4 months ago)

Author:

Micke Prag <micke.prag@…>

Branches:

('master', 'deebf2045e7119c339412580f37a1e653f7d5715')('controller-upgrade', '00f95d22e12d96ef089e0902ef62ae8ce841dc6f')

Children:

e384c5b677f7dad188b94035fa6972683981783a

Parents:

a26244fa951ae39b004b1dcf69685e7c70e9e41a

git-author:

Micke Prag <micke.prag@telldus.se>2012-01-23 11:12:46+01:00

git-committer:

Micke Prag <micke.prag@telldus.se>2012-01-23 11:12:46+01:00

Message:

Tried to clarify the fallback mechanism used in tdMethods()

File:

• docs/01-telldus-core.dox (modified) (1 diff)

docs/01-telldus-core.dox

@@ -95 +95 @@
  * \endcode
  *
- * By supplying the methods the application supports, the library can be backwards
- * compatible. Let's say that the client application only supports turning on and
+ * By supplying the methods your application supports, the library can return
+ * 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:
  * \code