.NET Customisation
User Guide
.NET Customisation
:
How to Write a CAF Addin
:
The IAddin Interface
: Addin Start-up Performance
Addin Start-up Performance
One of the benefits of keeping the application code separate from the code of associated controls, as recommended above, is that it makes it much easier to make separate decisions about when to undertake action especially, but not only, at start-up. It is normal that all windows, controls and dialogues are built and initialised when the addin starts up - normally when the AVEVA module (for example, the Engineering module or the DRAW module) starts up - but it is not necessary to populate it with data unless and until the window is shown. Unnecessary calculations of this kind can add appreciably to the time taken to start up the AVEVA module giving a poor user experience. Normally a slight delay at the point where the window in question is first shown goes almost unnoticed by the user and is therefore much more acceptable.
The principle of delaying calculations until the point where the result is required is known as "lazy evaluation". Lazy evaluation is useful not only at start up, but can also be used, for example, to limit the extent of calculation done. The NetGridControl, for example, exploits this to calculate fully only the part of the table which is visible at any one time, and thereby greatly improving responsiveness for large data sets.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.
