Updated properties reference

Author: BasicPrimitives

apireference/enums.md

@@ -161,14 +161,14 @@ Line style of connection lines.
  | `Solid` | number | `0` | Solid | 
 
 ## <a name="primitives.common.LoopsLayoutMode" id="primitives.common.LoopsLayoutMode">LoopsLayoutMode</a>
-Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, so majority of references ideally should go in one direction. This option allows to disable optimization and force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram.
+Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, so majority of references ideally should go in one direction. This option disables optimization and forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram.
 
  `primitives.common.LoopsLayoutMode` 
 
 | Name | Type | Value | Description | 
 | --- | --- | --- | --- | 
- | `KeepItemsOrder` | number | `1` | Keeps items levels order matching the order of items in the control configuration. | 
- | `Optimized` | number | `0` | Optimized. Control searches for layout producing minimal number of backward loops between levels. | 
+ | `KeepItemsOrder` | number | `1` | Keeps order of items on levels, the same as in `items` collection property. | 
+ | `Optimized` | number | `0` | Optimized. Control searches for layout producing minimal number of feedback loops in the diagram. | 
 
 ## <a name="primitives.common.NavigationMode" id="primitives.common.NavigationMode">NavigationMode</a>
 Interactivity mode. Control implements standard behaivour of classic desktop UI controls. It supports single selected node - cursor. It supports on mouse over node visual feedback - highlight. It supports selection of group of nodes - selected items. All that functionality can be disabled depending on your application requirements.

apireference/famdiagram.md

@@ -40,7 +40,7 @@ Family Chart configuration object. Use this object as a reference for available
  | `enableMatrixLayout` | boolean | `false` | This option enables automatic layout of nodes sharing the same set of parents and children in form of matrix. | 
  | `groupByType` | GroupByType | `2` | This property sets loose nodes alignment between rows. Nodes can be placed close towards parents or children. | 
  | `hideGrandParentsConnectors` | boolean | `false` | Set this property to enable hiding of direct connectors to grand parents. It helps to reduce diagrams connectors layout complexity. | 
- | `loopsLayoutMode` | LoopsLayoutMode | `primitives.common.LoopsLayoutMode.Optimized` | Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, so majority of references ideally should go in one direction. This option allows to disable optimization and force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram. | 
+ | `loopsLayoutMode` | LoopsLayoutMode | `primitives.common.LoopsLayoutMode.Optimized` | Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, so majority of references ideally should go in one direction. This option disables optimization and forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram. | 
  | `maximumColumnsInMatrix` | number | `6` | Sets maximum number of columns in the matrix formation. The matrix formation stays squared as long as total number of columns does not exceed this property value. In order to shape nodes into matrix formation they should share the same set of parents and children. See `enableMatrixLayout` property. | 
  | `minimalVisibility` | Visibility | `2` | Minimal nodes visibility in the diagram. If auto fit of the diagram into current page size is enabled, then this option controls minimum allowed size of the diagram nodes. | 
  | `minimumMatrixSize` | number | `4` | Sets Minimum number of nodes needed to be shaped into matrix formtion. In order to shape nodes in form of matrix they should share the same set of parents and children. See `enableMatrixLayout` property. | 

min/primitives.latest.js

@@ -2067,19 +2067,20 @@ primitives.common.LineType = {
 
 /**
  * Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, 
- * so majority of references ideally should go in one direction. This option allows to disable optimization and 
- * force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, 
- * then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram.
+ * so majority of references ideally should go in one direction. This option disables optimization and 
+ * forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, 
+ * then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be
+ * on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram.
  *  
  * @enum {LoopsLayoutMode}
  */
 primitives.common.LoopsLayoutMode = {
   /**
-   * Optimized. Control searches for layout producing minimal number of backward loops between levels.
+   * Optimized. Control searches for layout producing minimal number of feedback loops in the diagram.
    */
   Optimized: 0,
   /**
-   * Keeps items levels order matching the order of items in the control configuration.
+   * Keeps order of items on levels, the same as in `items` collection property.
    */
   KeepItemsOrder: 1
 };
@@ -7621,9 +7622,10 @@ primitives.famdiagram.Config = function (name) {
 
   /**
    * Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, 
-   * so majority of references ideally should go in one direction. This option allows to disable optimization and 
-   * force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, 
-   * then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram.
+   * so majority of references ideally should go in one direction. This option disables optimization and 
+   * forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, 
+   * then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be
+   * on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram.
    * 
    * @group Auto Layout
    * @type {LoopsLayoutMode}

src.primitives/Controls/FamDiagram/configs/Config.js

@@ -75,9 +75,10 @@ primitives.famdiagram.Config = function (name) {
 
   /**
    * Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, 
-   * so majority of references ideally should go in one direction. This option allows to disable optimization and 
-   * force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, 
-   * then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram.
+   * so majority of references ideally should go in one direction. This option disables optimization and 
+   * forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, 
+   * then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be
+   * on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram.
    * 
    * @group Auto Layout
    * @type {LoopsLayoutMode}

src.primitives/enums/LoopsLayoutMode.js

@@ -4,19 +4,20 @@
 
 /**
  * Loops layout mode. Configuration may contain loop references between items, so control tries to find layout minimizing number of loops between levels, 
- * so majority of references ideally should go in one direction. This option allows to disable optimization and 
- * force items level order to match their order in `items` collection. For example if you have two nodes `A` and `B` and each node references the other one as parent, 
- * then it is undetermenistic which node is going to be on the top. If this option is set to `KeepItemsOrder` then node be is going to be at the top level in the diagram.
+ * so majority of references ideally should go in one direction. This option disables optimization and 
+ * forces items levels order to match their order in `items` collection. For example if you have two nodes `A` and `B` referencing each other as a parent, 
+ * then it is not defined which one is going to be on the top of the diagram. Set this option to `KeepItemsOrder`, if you need the first item in your collection to be
+ * on the top, otherwise control will optimize loops layout in order to minimize number of loops in diagram.
  *  
  * @enum {LoopsLayoutMode}
  */
 primitives.common.LoopsLayoutMode = {
   /**
-   * Optimized. Control searches for layout producing minimal number of backward loops between levels.
+   * Optimized. Control searches for layout producing minimal number of feedback loops in the diagram.
    */
   Optimized: 0,
   /**
-   * Keeps items levels order matching the order of items in the control configuration.
+   * Keeps order of items on levels, the same as in `items` collection property.
    */
   KeepItemsOrder: 1
 };