J
Jim Rambo
I am new to VBscript and PPT macros. I ordered David Marcovitz's book, but
until it arrives, I'm pretty much in the dark as to best practices for
developing reusable macros that span multiple templates and are simple to
maintain.
It seems to be a recurring theme in my group that we want to loop through
our presentations and perform a given operation on the same graphic object
for each slide, for example writing the title text or main body text on each
slide to a file. Furthermore, we may need to process presentations from
other groups using different templates.
To do this, I envision having to do something like the following:
1) create a template (for reuse on multiple presentations)
2) name and store the graphic objects on the slide/title master layouts
(possibly using a macro)
3) create new slides using the one of the layouts, or insert slides from
another presentation and reapply the layout (possibly using a macro)
4) run the slide processing operation of choice.
Does this seem like overkill, or is there a simpler, more maintainable way
to do this?
Your suggestions are greatly appreciated - Jim
until it arrives, I'm pretty much in the dark as to best practices for
developing reusable macros that span multiple templates and are simple to
maintain.
It seems to be a recurring theme in my group that we want to loop through
our presentations and perform a given operation on the same graphic object
for each slide, for example writing the title text or main body text on each
slide to a file. Furthermore, we may need to process presentations from
other groups using different templates.
To do this, I envision having to do something like the following:
1) create a template (for reuse on multiple presentations)
2) name and store the graphic objects on the slide/title master layouts
(possibly using a macro)
3) create new slides using the one of the layouts, or insert slides from
another presentation and reapply the layout (possibly using a macro)
4) run the slide processing operation of choice.
Does this seem like overkill, or is there a simpler, more maintainable way
to do this?
Your suggestions are greatly appreciated - Jim