Limit a calculateNow script to a single page or pages?

Question

Currently I am using the following script I found by Thom Parker to create a button that toggles automatic calculations on and off:

if(event.target.borderStyle == border.b){
// Perform Push Down Actions
event.target.borderStyle = border.i;
event.target.buttonSetCaption("Turn Calculations On");
// Darken Down Colors
event.target.textColor = ["RGB", 0.8, 0.8, 0.4];
event.target.fillColor = ["RGB", 0, 0, 0.7];
// Turn Calculations Off
this.calculate = false;
}else{
// Perform Pop Up Actions
event.target.borderStyle = border.b;
event.target.buttonSetCaption("Turn Calculations Off");
// Restore Up Colors
event.target.textColor = ["RGB", 1, 1, 2/3];
event.target.fillColor = ["RGB", 0, 0, 1];
// Turn Calculations On
this.calculate = true;
this.calculateNow();

Would it be possible to limit turning the automatic calculations on and off to a specific page or range of pages? I have over 600 radio buttons and limiting the calculation to a single page and/or a range of pages would really speed things up! Thank you for your help!

Thom Parker · Accepted Answer

There are a few ways to handle too many calculations.

1. Only use calculation scripts were necessary.

2. Setup the form scripts so calculations aren't causing looping cascades.

3. Qualify calculations so they aren't being performed unnecessarily. The event.source property is the field that triggered the calculation. It is null on a form reset and when importing data.

4. A more controlled version of #3 is to put multiple calculations into a single script (as suggested by JR), then use event.source to selectively execute only the calculations that are necessary. You could divide calculations per page by putting all the calcs for a single page into a text field on that page, then use this code to qualify it.

if(!event.source || (event.target.page == event.source.page))

{

}

This only works if target and source are really on the same page, and neither field has more then one instance.

JR Boulay · Answer

The answer is no.To speed things up, there is another method: instead of putting calculation operations in a multitude of fields, it's better to put all the calculations (for a page, for example) in a single field, possibly hidden. This also has the advantage of making modifications and maintenance easier, because all the calculations are in the same place.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded