Changeset df58f9 for docs/telldus-core.dox

Timestamp:

10/28/11 15:40:10 (19 months ago)

Author:

Micke Prag <micke.prag@…>

Branches:

('master', 'a231b56d57a69513303d0061f5fa3e3cd51c85c1')('controller-upgrade', '72b31cc86eeeef18f1371a3067b6e8a5ca21abfc')('windows_service_fixes', 'df6bd2788365991d36d5af2a75833b8de2a5860f')

Children:

478e8cdb738ff0945da80362da00a28e17746150

Parents:

fc626ef7094410ba93e3fd82a9392bd307924d99

git-author:

Micke Prag <micke.prag@telldus.se>2011-10-28 14:15:39+02:00

git-committer:

Micke Prag <micke.prag@telldus.se>2011-10-28 15:40:10+02:00

Message:

Make sure lines not exceeding 80 chars

File:

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

docs/telldus-core.dox

@@ -213 +213 @@
  * Many devices (for example motion detectors) resends their messages many times
  * to ensure that they are received correctly. If a deviceeventcallback or
- * rawdeviceeventcallback in turn is calling a controlling function, for example tdTurnOn,
- * it may be neccessary to implement some solution to wait for the device to finish its
- * resending, before executing the controlling function. See how this can be done in the python example.
+ * rawdeviceeventcallback in turn is calling a controlling function, for example
+ * tdTurnOn, it may be neccessary to implement some solution to wait for the
+ * device to finish its resending, before executing the controlling function.
+ * See how this can be done in the python example.
  *
  * \subsection sec_events_callbacks Callbacks