Changes between Version 4 and Version 5 of XmlModelConfiguration


Ignore:
Timestamp:
Feb 18, 2011, 8:25:29 PM (13 years ago)
Author:
Torben Dannhauer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • XmlModelConfiguration

    v4 v5  
    1313   - label: text to label the model with.
    1414   - dynamic: "yes" to add an standard updater to the model.
    15    - position: Position to place the model
    16    - attitude: Orientation in degree to place the model
    17    - updater [optional]: Channels to use for position, attitude and label update
    18    - cameraoffset [optional]: Rotational (in degree) and translational offset for the object mounted camera manipulator to the visual_object   
    19    - Geometry [optional]: 3D model to display. Leave empty to use model without 3D model.
    20    - Geometryoffset [optional]: Rotational offset (in degree) for the loaded 3D model to the visual_object (if the 3D model has a wrong coordinate frame)
    21    - Geometryscale [optional]: Scale factors for the loaded 3D model in all three dimensions.
    2215-->
    2316<model objectname="TestObject" trackingid="1" label="TestText!" dynamic="no">
     
    4235
    4336== Position & Attitute ==
     37To position the visual_object, you have to setup a location in latitude (in degree), logitude (in degree) and altitude. Additionally you have to specify it's attitude in degree.
    4438{{{
    4539#!xml
     
    4943
    5044== Updater ==
     45To update certain properties of the visual_object, you can define an updater and configure the slot names which should be used for the updates.
     46The attributes in the XML entries are not values but names of the slots which content should be used for updating the visual_object every frame.
     47To skip updating of a certain value, leave the updatername emtpy.
     48
     49The updater can be defined in the XML configuration file as followed:
    5150{{{
    5251#!xml
    5352<updater>
    54  <position lat="" lon="" alt=""></position>
    55  <attitude rot_x="" rot_y="" rot_z=""></attitude>
     53 <position lat="your_lat_slot" lon="your_lon_slot" alt=""></position>
     54 <attitude rot_x="your_rot_x_slot" rot_y="" rot_z="your_rot_z_slot"></attitude>
    5655 <label text=""></label>
    5756</updater>
     
    5958
    6059== Camera Offset ==
     60To use the "Object mounted" camera manipulator, you have to define for your what the camera coordinates relative to your visual_object are. You can define a rotational (in degree) und translational offset.
     61
     62The defition of the camera offset in the XML configuration file is:
    6163{{{
    6264#!xml
     
    6870
    6971== Geometry ==
    70 Using a geometry as well as modifying it with offset or scalefactors is optional.
     72You can load and display a 3D geometry to visualize the 3D object. You have to specify the filename with an relative or absolute path.
     73If the 3D model has the wrong orientation or wrong size, you can specify an offset rotation (in degree) or scale factors. Using a geometry as well as modifying it with offset or scalefactors is optional.
    7174
    72 You can load and display a 3D geometry to visualize the 3D object. You have to specify the filename with an relative or absolute path.
    73 If the 3D model has the wrong orientation or wrong size, you can specify an offset rotation or scale factors.
    74 
    75 The XML configuration of an gemoetry entry in a visual object is:
     75The XML configuration of an geometry entry in a visual object is:
    7676{{{
    7777#!xml
     
    8282}}}
    8383
    84 
    85 
     84If you do not use a geometry, a visual_object is still usefull, e.g. for dynamic positioning and upating a text label or to attach the camera.