From 51c44f09553b13194ee8346266b0930d1a135590 Mon Sep 17 00:00:00 2001 From: Raimo Niskanen Date: Fri, 19 May 2017 11:52:35 +0200 Subject: Fix documentation details --- lib/stdlib/doc/src/gen_statem.xml | 4 ++-- system/doc/design_principles/statem.xml | 12 +++++++----- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/lib/stdlib/doc/src/gen_statem.xml b/lib/stdlib/doc/src/gen_statem.xml index bc86415d28..e71de1523b 100644 --- a/lib/stdlib/doc/src/gen_statem.xml +++ b/lib/stdlib/doc/src/gen_statem.xml @@ -4,7 +4,7 @@
- 2016-2017 + 20162017 Ericsson AB. All Rights Reserved. @@ -344,7 +344,7 @@ ok

To compare styles, here follows the same example using callback mode - state_functions, or rather the code to replace + handle_event_function, or rather the code to replace after function init/1 of the pushbutton.erl example file above:

diff --git a/system/doc/design_principles/statem.xml b/system/doc/design_principles/statem.xml index f01615fdcd..7febe31df3 100644 --- a/system/doc/design_principles/statem.xml +++ b/system/doc/design_principles/statem.xml @@ -4,7 +4,7 @@
- 2016-2017 + 20162017 Ericsson AB. All Rights Reserved. @@ -1582,10 +1582,12 @@ format_status(Opt, [_PDict,State,Data]) -> for example, a complex state term like a tuple.

- One reason to use this is when you have - a state item that affects the event handling, - in particular in combination with postponing events. - We complicate the previous example + One reason to use this is when you have a state item + that when changed should cancel the + state time-out, + or one that affects the event handling + in combination with postponing events. + We will complicate the previous example by introducing a configurable lock button (this is the state item in question), which in the open state immediately locks the door, -- cgit v1.2.3