<< 点击显示目录 >> 主页  mappView帮助助手 > mapp View帮助信息 > Widgets  > Data  > Table  > Concept  > Optimizing widget "Table"

This section explains how to optimize the speed for updating data or maximize the performance of the table.

The prerequisite for optimization is that data is constantly updated. Otherwise, no optimizations can be performed.

This use case is only for tables that are continuously updated with data.

•The following properties can be used for optimization:

•stopRefreshAtScroll (true)

•tableConfiguration (use)

•filterConfiguration (do not use)

•dataOrientation (vertical)

•useTableStyling (true)

•refreshRate (optimize)

stopRefreshAtScroll

Preferred value: true

With "stopRefreshAtScroll=true", the table is no longer updated while scrolling.

If the table receives new data, all old rows are removed and the new ones added.

If scrolling takes place during this process, the table will attempt to place the user at the position where the table was before the update.

This results in poor performance of the table and decreased usability.

This property makes scrolling in the table much smoother and improves the appearance of the user interface.

tableConfiguration

Preferred value: true

This property has a great effect on performance since it allows the visibility of table elements to be set.

The speed of the table can be increased considerably by removing unneeded rows and columns.

The general rule is that fewer cells (rows multiplied by cells) result in faster display of the table.

This is particularly noticeable on low-end target systems where the number of cells really counts.

The table cuts out the data set in tableConfiguration, which means that fewer rows/columns are available for the table and the update runs more smoothly.

If tableConfiguration is updated at runtime, however, the table must be restarted. This procedure should be avoided.

filterConfiguration

Preferred value: Should not be used.

The complexity of the filter mechanism can influence the table. For optimized display, the filter mechanism should not be used.

This property should be avoided. tableConfiguration can be used as much as possible instead.

dataOrientation

Preferred value: vertical

The vertical alignment of a table is the most commonly used. For this reason, the data in a table is structured vertically by default. Horizontal alignment first requires data restructuring, which can affect performance. For this reason, vertical alignment is recommended for an optimized display.

showSortingButtons (if dataOrientation=horizontal)

Preferred value: false

If horizontal alignment is required, the sort buttons should be avoided if possible.

Sorting the data in a table affects performance. For this reason, it is recommended not to use the sort buttons.

useTableStyling

Preferred value: false

Another possibility for optimizing the table is to avoid individual styling. Using this property can affect the performance of the table.

refreshRate

Preferred value: ≥200 ms

The refresh rate must take into account the total number of cells and the hardware used.

The total number of cells is the number of cells available after properties tableConfiguration and filterConfiguration are applied.

The following are some reference values for a T50.

This should also be adapted to the number of other widgets/components on the same page, however. So the higher the number of widgets/components, the higher the refreshRate.

A T80 does not require an optimized refresh rate. It is recommended to use 400 ms for large tables.