File: Concepts.MockNodes.txt

package info (click to toggle)
openni 1.5.4.0%2Bdfsg-4
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 44,844 kB
  • sloc: cpp: 116,706; ansic: 58,777; sh: 10,287; cs: 7,698; java: 7,402; python: 1,541; makefile: 492; xml: 167
file content (16 lines) | stat: -rw-r--r-- 714 bytes parent folder | download | duplicates (7)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
/**
@page conc_mocks Mock Nodes

OpenNI provides a "mock" implementation for nodes. A "mock" 
implementation does not have any logic of its own. Instead, it lets an 
outside component to feed configuration changes and data into it. For 
example, mock nodes are used by Player nodes to simulate actual nodes 
when reading data from a recording. 

Mock nodes can also be used when wanting to record something other than 
actual nodes. An application may create a mock node, copy into it the 
state of another node (initial configuration), and then read data from 
the original node and write it to the mock node. Then, the mock node can 
be recorded. See @ref nirecordsynthetic for such a sample. 

*/