I'm trying to figure out how to get a value in a field in a custom dialog to stick each time the dialog script is run until it is changed. Then when the script is run again the new value is there.
I'm not getting it.
Persistent or global variable
2011-12-06 11:32:47
My Product Information:
Acrobat Pro Extended 9.4.3, Windows
Acrobat Pro Extended 9.4.3, Windows
2011-12-06 11:50:50
#2
Hi Steven,
The dialog value is getting re-initialized for one of two reasons.
1. The entire dialog object is being recreated
2. the "initialize" member of the dialog object is setting the value.
For #1, make sure the dialog object is defined only once. If this is a document, then the dialog object should be defined in a document level script, if this is a folder level script, then the dialog object should be defined in the main body of code, not within a function.
If #2 is the issue, make sure value acquired when the dialog is closed, is then used to initialize the dialog field when it is restarted. I do this by adding a member to the dialog object for each value that will be passed in and out of the dialog. This member is used to initialize the dialog values and to capture the value on close. If the dialog object is not reinitialized, then this value remains stable.
The dialog value is getting re-initialized for one of two reasons.
1. The entire dialog object is being recreated
2. the "initialize" member of the dialog object is setting the value.
For #1, make sure the dialog object is defined only once. If this is a document, then the dialog object should be defined in a document level script, if this is a folder level script, then the dialog object should be defined in the main body of code, not within a function.
If #2 is the issue, make sure value acquired when the dialog is closed, is then used to initialize the dialog field when it is restarted. I do this by adding a member to the dialog object for each value that will be passed in and out of the dialog. This member is used to initialize the dialog values and to capture the value on close. If the dialog object is not reinitialized, then this value remains stable.
2011-12-06 12:41:59
#3
Thanks guys for the responses. I'm afraid I'm not as proficient at coding as you guys so I'm struggling trying to make sense of this stuff. Thanks for the input.
I'm trying to create own PDF Splitter and am running the current version as a batch in Acrobat 9 and eventually want to run it via a tool bar button.
I'm trying to create own PDF Splitter and am running the current version as a batch in Acrobat 9 and eventually want to run it via a tool bar button.
2011-12-07 10:22:08
#4
Is there an example that shows how #2 works that I can look at and try to decipher?
2011-12-08 13:10:35
#5
Per your question about adding a toolbar button to Acrobat. See Thom's post:
Executing Acrobat Menu Items from JavaScript.by Thom Parker
¯
Jun 30, 2008
Topics: JavaScript
http://acrobatusers.com/tutorials/2008/06/executing_menu_items_from_javascript
Search this forum and read to learn is my advice. It has helped me out immensely.
I've created a lot of buttons (really labels) to the Add-on Tools Toolbar to automate many redundant procedures.
Executing Acrobat Menu Items from JavaScript.by Thom Parker
¯
Jun 30, 2008
Topics: JavaScript
http://acrobatusers.com/tutorials/2008/06/executing_menu_items_from_javascript
Search this forum and read to learn is my advice. It has helped me out immensely.
I've created a lot of buttons (really labels) to the Add-on Tools Toolbar to automate many redundant procedures.
global.radius = 8; // Declare radius to be a global variable
global.setPersistent("radius", true); // Now say it’s persistent across sessions
(some time later...)
console.println("The value of global.radius is" + global.radius);
(and to kill it...)
delete global.radius;
Note that you can only set persistence on booleans, numbers and strings; and there's a very small storage limit.