File: Main.cpp

package info (click to toggle)
boost 1.34.1-14
  • links: PTS
  • area: main
  • in suites: lenny
  • size: 116,412 kB
  • ctags: 259,566
  • sloc: cpp: 642,395; xml: 56,450; python: 17,612; ansic: 14,520; sh: 2,265; yacc: 858; perl: 481; makefile: 478; lex: 94; sql: 74; csh: 6
file content (110 lines) | stat: -rw-r--r-- 3,161 bytes parent folder | download | duplicates (20)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
//////////////////////////////////////////////////////////////////////////////
// Copyright 2002-2006 Andreas Huber Doenni
// Distributed under the Boost Software License, Version 1.0. (See accompany-
// ing file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
//////////////////////////////////////////////////////////////////////////////



//////////////////////////////////////////////////////////////////////////////
// This program shows how a state machine can be spread over several
// translation units if necessary. The inner workings of a digital camera are
// modeled, the corresponding state chart looks as follows:
//
//  ---------------------------
// |                           |
// |      NotShooting          |
// |                           |
// |        -------------      |<---O
// |  O--->|   Idle      |     |                    --------------
// |        -------------      |   EvShutterHalf   |              |
// |          |  ^             |------------------>|   Shooting   |
// | EvConfig |  | EvConfig    |                   |              |
// |          v  |             |  EvShutterRelease |              |
// |        -------------      |<------------------|              |
// |       | Configuring |     |                   |              |
// |        -------------      |                    --------------
//  ---------------------------                              
//
// The states Configuring and Shooting will contain a large amount of logic,
// so they are implemented in their own translation units. This way one team
// could implement the Configuring mode while the other would work on the
// Shooting mode. Once the above state chart is implemented, the teams could
// work completely independently of each other.



#include "Precompiled.hpp"
#include "Camera.hpp"
#include <iostream>



//////////////////////////////////////////////////////////////////////////////
char GetKey()
{
  char key;
  std::cin >> key;
  return key;
}


//////////////////////////////////////////////////////////////////////////////
int main()
{
  std::cout << "Boost.Statechart Camera example\n\n";

  std::cout << "h<CR>: Press shutter half-way\n";
  std::cout << "f<CR>: Press shutter fully\n";
  std::cout << "r<CR>: Release shutter\n";
  std::cout << "c<CR>: Enter/exit configuration\n";
  std::cout << "e<CR>: Exits the program\n\n";
  std::cout << "You may chain commands, e.g. hfr<CR> first presses the shutter half-way,\n";
  std::cout << "fully and then releases it.\n\n";


  Camera myCamera;
  myCamera.initiate();

  char key = GetKey();

  while ( key != 'e' )
  {
    switch( key )
    {
      case 'h':
      {
        myCamera.process_event( EvShutterHalf() );
      }
      break;

      case 'f':
      {
        myCamera.process_event( EvShutterFull() );
      }
      break;

      case 'r':
      {
        myCamera.process_event( EvShutterRelease() );
      }
      break;

      case 'c':
      {
        myCamera.process_event( EvConfig() );
      }
      break;

      default:
      {
        std::cout << "Invalid key!\n";
      }
      break;
    }

    key = GetKey();
  }

  return 0;
}