|
|
|
@ -185,7 +185,7 @@ mobile-csv-file = /usr/local/etc/owlps/mobiles.csv
|
|
|
|
|
# the path defined here should "link" (include) all the capture points
|
|
|
|
|
# that are going to be used for this kind of autocalibration.
|
|
|
|
|
# In the string, the values are separated by semicolons, and each group
|
|
|
|
|
# of coordinates can optionnaly be surrounded by parenthesis. The two
|
|
|
|
|
# of coordinates can optionally be surrounded by parenthesis. The two
|
|
|
|
|
# following examples, which declare a path following the points (1;1;1),
|
|
|
|
|
# (10;1;1) and (10;10;1), are equivalent:
|
|
|
|
|
#generated-line-path = (1;1;1);(10;1;1);(10;10;1)
|
|
|
|
@ -198,7 +198,7 @@ mobile-csv-file = /usr/local/etc/owlps/mobiles.csv
|
|
|
|
|
|
|
|
|
|
# When generate-reference-points includes "list", the list of reference
|
|
|
|
|
# points declared here is be generated. In the string, the values are
|
|
|
|
|
# separated by semicolons, and each group of coordinates can optionnaly
|
|
|
|
|
# separated by semicolons, and each group of coordinates can optionally
|
|
|
|
|
# be surrounded by parenthesis. The two following examples, which
|
|
|
|
|
# declare the points (1;2;1) and (4;2.5;1), are equivalent:
|
|
|
|
|
#generated-points-list = (1;2;1);(4;2.5;1)
|
|
|
|
|