TOC : Script API > JavaScript > JavaScript Events > OnBind > Script Execution Order >

 

Component Script Execution Order

<< Click to Display Table of Contents >>

Navigation:  »No topics above this level«

TOC : Script API > JavaScript > JavaScript Events > OnBind > Script Execution Order >

 

Component Script Execution Order

 

 

By default, component scripts in a band are executed in the sequential order in the component tree. And if a report is bound to multiple pages, script executions are repeated as many as the number of pages. If a component have child components (crosstab, table, ganttchart, region, etc.), after the script of the parent is executed, scripts of the child are repeatedly executed. Chart component is a single component with no child and follows the sequential execution order.

A fixed table component cannot have its own script, but its child label can have a script. So each fixed table label is treated as a single component.

 

Script execution order of single components (label, note, chart, fixed table label) and container components (crosstab, ganttchart, table) and region component is described below:

 

 

Controlling script execution order :

 

To change script execution order of a component, use [Bring to Front], [Send to Back], [Bring Forward], [Send Backward] of [Order] in the component popup menu.

 

 

Auto size property of a label and changing of its text properties :

 

Auto Size property of a label applies only one time at label creation time. Once created and auto sized, the label cannot be resized. Hence, Even if auto size property of a label was set, when you change word wrap property or text contents of the label by a script of other label after label creation,  the label will not be auto resized. This can be avoided by executing first the script of other label which modifies text properties of the label to be auto sized.

 

 

A note on changing of component position :

 

At the 1st step scripts, the coordinates of a single or container component represents the relative position in the band. After executing the 1st step scripts, however, the coordinates is converted to the position based on the page. Hence, at the 2nd step,  setting the coordinates of a child component changes its position base on the page, not the band.