G
Guest
I have ~50 shapes that I want to apply various fill and line specs to
programatically. (The macro to assign the fill and line specs likely would be
run now and then, not frequently.)
Currently I'm using a pair of tags (myFillSpec and myLineSpec) for each
shape, planning to use macros to assign the fills and lines based on the
tags' values. For example:
If myShape.Tags("myFillSpec") = "NoFill" Then myShape.Fill.Visible =
False
However, I started thinking that I may have read somewhere that each tag you
apply has a significant toll in terms of system overhead...
With ~50 shapes, each with (the same) two tags, am I creating enough of a
burden to worry about this (and go with more cumbersome shape names)?
Does the "overhead" come with each tag (2), or with each application of the
tags (~100, in this example)?
Is there somewhere I can read up on considerations for using tags versus
using other approaches?
Thanks much for any guidance or suggestions y'all can offer.
LM
programatically. (The macro to assign the fill and line specs likely would be
run now and then, not frequently.)
Currently I'm using a pair of tags (myFillSpec and myLineSpec) for each
shape, planning to use macros to assign the fills and lines based on the
tags' values. For example:
If myShape.Tags("myFillSpec") = "NoFill" Then myShape.Fill.Visible =
False
However, I started thinking that I may have read somewhere that each tag you
apply has a significant toll in terms of system overhead...
With ~50 shapes, each with (the same) two tags, am I creating enough of a
burden to worry about this (and go with more cumbersome shape names)?
Does the "overhead" come with each tag (2), or with each application of the
tags (~100, in this example)?
Is there somewhere I can read up on considerations for using tags versus
using other approaches?
Thanks much for any guidance or suggestions y'all can offer.
LM