Index: trunk/doc/developer/lihata_format/root_view.lht =================================================================== --- trunk/doc/developer/lihata_format/root_view.lht (revision 23052) +++ trunk/doc/developer/lihata_format/root_view.lht (revision 23053) @@ -1,6 +1,6 @@ ha:lht_tree_doc { ha:roots { - ha:view-list-v1 { + ha:view-list-v* { type=li desc={a list of view items (locations and objects to highlight on the board, e.g. for DRC violations)} li:children { Index: trunk/doc/developer/lihata_format/tree.html =================================================================== --- trunk/doc/developer/lihata_format/tree.html (revision 23052) +++ trunk/doc/developer/lihata_format/tree.html (revision 23053) @@ -207,19 +207,19 @@    floater flag   subc part can be moved after subc placing   ha:data     Layers and global objects of the board -> -

li:view-list-v1

+

li:view-list-v*

type:name value ver description -
li:view-list-v1     a list of view items (locations and objects to highlight on the board, e.g. for DRC violations) -
 ha:view.ID     a view item; ID is a 32 bit signed integer, unique within the view list -
  type string   free form short text for type of the entry; the GUI may group items by type -
  title string   free form short text for the title of the entry; the GUI typically uses this in brief listings -
  description string   free form long text for the detailed description of the entry -
  li:bbox coord   optional: 4 coordinates in x1;y1;x2;y2 order that describes the bounding box of the view in board space coordinates; when available, the preview or go-to will use this for view box -
  li:xy coord   optional: 2 coordinates in x;y order that describes a specific board location -
  li:objs.ID     a group of related objects; there should be at most two groups with ID 0 and 1. These objects are often highlighted in red and blue. -
   li:id     objects are specified as a list of object IDs (32 bit integers) +
li:view-list-v*     a list of view items (locations and objects to highlight on the board, e.g. for DRC violations) +
 ha:view.ID     a view item; ID is a 32 bit signed integer, unique within the view list +
  type string   free form short text for type of the entry; the GUI may group items by type +
  title string   free form short text for the title of the entry; the GUI typically uses this in brief listings +
  description string   free form long text for the detailed description of the entry +
  li:bbox coord   optional: 4 coordinates in x1;y1;x2;y2 order that describes the bounding box of the view in board space coordinates; when available, the preview or go-to will use this for view box +
  li:xy coord   optional: 2 coordinates in x;y order that describes a specific board location +
  li:objs.ID     a group of related objects; there should be at most two groups with ID 0 and 1. These objects are often highlighted in red and blue. +
   li:id     objects are specified as a list of object IDs (32 bit integers)

Common subtrees

Each table below describes a subtree that usually does not specify a whole tree (thus they are usually not a valid file on their own). These subtrees are described in a separate table because they are used from multiple other trees. Index: trunk/doc/developer/lihata_format/tree.txt =================================================================== --- trunk/doc/developer/lihata_format/tree.txt (revision 23052) +++ trunk/doc/developer/lihata_format/tree.txt (revision 23053) @@ -197,10 +197,10 @@ floater flag subc part can be moved after subc placing ha:data Layers and global objects of the board -> -li:view-list-v1 +li:view-list-v* type:name value ver description -li:view-list-v1 a list of view items (locations and objects to highlight on the board, e.g. for DRC violations) +li:view-list-v* a list of view items (locations and objects to highlight on the board, e.g. for DRC violations) ha:view.ID a view item; ID is a 32 bit signed integer, unique within the view list type string free form short text for type of the entry; the GUI may group items by type title string free form short text for the title of the entry; the GUI typically uses this in brief listings