Digital Workshop

Hi

I'm working on a complex publication in 05XE that will likely, when completed, have several hundred publication variables storing information to the registry, plus several hundred actions. Since the pre-set Opus actions (for example, any action, like "go to page," "write to registry" not needing scripting) are easier to use than scripting, I am constantly using the small script editor for 2 main buttons. These 2 script editor boxes contain an enormous number of lines, mixing pre-set actions with script (when a pre-set action isn't available). While I could probably turn pre-set actions into script and possibly even use the larger script object, this would take alot longer (for example, copying and pasting the registry key pathway each time instead of a simple 'write or read to registry' action).

My questions:

(1) Can Opus and the registry hold a very large number of variables or will they run out of space?
(2) Can the small script editor hold a very large number of actions allowing me to simply keep going forward adding more?

If possible, I would like to simply keep going forward, but would prefer not to spend countless hours working on this project only to find out I "ran out of road" with the registry, variable space or script editor capacity, having to discard all my work and start over.

I hope someone who has been down this path can shed some light.

Kind Regards,
Stephen
swartel@nycap.rr.com
05XE

Both could run out eventually, but I think you'd have to be into the millions and possibly billions to reach that point.

Let us know if you get there.

Purely in the interests of organisation you might find it simpler to put multiple script objects on the page and put your script functions in those, rather than putting them all into a couple of huge actions.

Hi Dave and Duncan

Thanks for your replies.

I'm unfamiliar with using script objects. A critical factor will be whether a single button's actions (for example "save"all the positions of the dragged and dropped vector objects on the page) scripted into one can run properly. When I experimented and tried to lump multiple script actions in the script editor, to make my task easier, it didn't run well. I abandoned the attempt and re-did these as separate scripts. It may well have been that there were other script errors (like an absent " or () causing it not to work correctly).

So, I'm going to try again to lump scripts together in a script object. The script object interface is larger, easier to use and has more functionality, like find and replace. If I can get it working (and, in run time, running) correctly, copying, pasting, find and replace would be alot easier and faster for this large job. Technically, I can't see why lumping them together won't work, since the button and script editor has them together, although sequential, one action or scrip after another.

Another challenge: finding and translating all of the triggers/actions that were pre-set in Opus (for example, "left mouse click," "right mouse click") into correct script actions.

Any ideas will be appreciated.

Kind Regards,
Stephen

Just call the functions in the script objects from the script actions.

So you have the normal Left Mouse CLick trigger (for example) with a Script action in it that calls the function MyLeftClickFn() (for example) which is declared in a script object on the page.

Hi

Thanks for the ideas. While I've yet to figure out how to use the script object, since I'm still unable to set up a trigger in it like a single left mouse click to initiate all the script that follows, I was able to resolve issues and keep going forward:

(1) I did set up additional buttons to hold the script actions. It appears that you can place one atop the next, and they all work at the same time when clicked. This avoids placing enormous numbers of actions and scrip into any one. I wonder if it's even possible to add a frame to hold all buttons stacked together.

(2) The script editor can be resized on the screen to make it larger and easier to work in (not as crowded).

These 2 solutions work fine.

Thanks again,
Stephen