00098: need a method to defined camera parameters via USERDATA mechaism

« 00097 | Issues | 00099 »

Summary: need a method to defined camera parameters via USERDATA mechaism

Created: 2008–09–02 13:37

Status: Released

Category: Request

From: frankie

Version: 1.1

Released_In: 2.0

Description:
the keybinds come with a method to define parameters for each camera, such as pan and tilt limits. This is specified via a file within the release. It would be good if an additional file within the userdata directory was read in addition.

---

Comments

frankie September 02, 2008, at 01:51 PM: In versions > 2.0, this will be done via "userdata/options/cam.user". For versions prior to 2.0, you can work around this by creating a file in your options directory (in the EDGE release) called cam.CEV.

This file would have the same syntax as cam.default in that directory. For example, to make the CEV_boresight camera fixed (unmovable), you might have the following:

#
# CAMERA MAPPING FILE
# where the format is as follows (one line per camera definition)
#
# cam_name  pan_name min_pan max_pan +/- tilt_name min_tilt max_tilt +/- vehicle_name
#
#
CEV_boresight "NULL" 0 0 + "NULL" 0 0 + cev

That would limit that camera from being translated or panned/tilted. Use cam.default as a reference but try not to edit it. Again, in versions after 2.0, this will be fixed by reading in a file "userdata/options/cam.user". —FG

---

« 00097 | Issues | 00099 »

Associated Commits

| commit | a0c8722bcbcc81ca5dddcf70a2ad6bd4ed010750 link5 | || | Author: | Frank Graffagnino | | Date: | Tue Sep 2 13:48:19 2008 -0500 | | Message: | [@Issue 00098: Added userdata mechanism to define camera limit params This is done by a file "userdata/options/cam.user" @] |

Affected Files:

.doug_blank_cshrc         | 1 +
 .doug_cshrc               | 1 +
 gui/keybinds.tcl          | 8 ++++++++
 userdata/options/cam.user | 8 ++++++++
 4 files changed, 18 insertions(+)