Differences

This shows you the differences between two versions of the page.

--- visual_object_array_tip [2021/07/22 13:02] – [The solution] emozolyak
+++ visual_object_array_tip [2022/01/16 15:14] (current) – ↷ Links adapted because of a move operation 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Object array visualization tip ======
-There is a limit in the dashboard object size due to certain performance issues. Sometimes users need a very big and rich dasboard visualization, which may lead to excceding this limit.
+There is a limit in the dashboard object size due to certain performance issues (not more than 199 elements or more than 400000 bytes)). Sometimes users need a very big and rich dasboard visualization, which may lead to excceding this limit.
 In this cases, some optimization trick maybe used.
@@ Line 8: / Line 8: @@
 === Example 1 - coke furnaces complex ===
 Along the raw of ~60 furnaces, a process state needed to be shown in the furnace place, from both sides, which means ~120 graphical objects.
-{{ ::screen_shot.jpg?direct&600 |}}
+{{ network:screen_shot.jpg?direct&600 |}}
 === Example 2 - big drying furnace ===
 There is an array of burners inside the furnace, each of the burner requires a set of binary indicators, which require a huge amount of visualization elements.
-{{ ::дашборд_сушило_cleaned.png?direct&600 |}}
+{{ network:дашборд_сушило_cleaned.png?direct&600 |}}
 ==== The solution ====
@@ Line 19: / Line 19: @@
 The solution was to pack all the elements into one string object, with each character reflecting the state of the respective process object.
-The idea is shown on the following gif image:
+The idea is shown on the following gif images:
-{{ :2021-07-22_15-51-00.gif?direct |}}
+{{ network:2021-07-22_15-51-00.gif?direct |}}
+{{ network:2021-07-22_17-18-41.gif?direct |}}
 == The code which makes the trick ==
@@ Line 62: / Line 64: @@
 </code>
+Using the font size and spacing adjusment in the lua script you can get necessary dimensions of this object.