> A global image pool is a useful feature for many LCL apps, not only the
IDE.
> That's why I don't see how a TIDEImageTypeSet would fit.
In that case the relative path to the resource is by definition a unique
identifier of the resource. In the following xml item
<Item1 Size="22x22" Path="\tango-icon-theme\22x22\apps"
FileName="accessories-text-editor.xpm" Class="apps"
Enum="iiAccessoriesTextEditor22x22" />
Path + FileName could be used as identifier (and made into one). Enum and
Size can be discarted. Although size could be used in controls to set or
check the size.
> > One thing I'm
> > not sure of is that if you change at designtime then you must be sure
that
> > changes are globally. That is why I use an XML file and create
> > resourcefiles from it that are linked in the binary.
>
> The xml file and the resource file(s) are needed anyway.
Yes, if you can only select a path at designtime. You cannot add a new image
(or any other resource), unless the management of the ideimage.xml (or
however it's called) and the ideres tool are integrated in Lazarus. Come to
think of it, I believe they should be integrated eventually and made part of
a project.
Darius Blaszijk
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
