Re: ? Segregating a Dialog's Code (Particularly Resources)

Hi,

I'm trying to figure out a way to separate a dialog's code (header,
implementation and resources) from the main app so that it is easy to copy
into
other projects (making my own Common Control so to speak).

I have put the dialog's code in a separate file (in a subdirectory of the
main
project), and can easily include that as needed. The problem is the
resources. I
know that you can use multiple resource files (hence RC2, etc.), but
apparently
some resource types (eg icons) are not compatible with separate resource
files.
I can put the dialog resource and guidelines, etc. in a dedicated RC file
and
include that, but once I start adding icons, it breaks (specifically, I
get the
duplicate resource ICON:1 resource compiler error).

I don't want to go the resource-only-DLL route, I am just trying to figure
out
how resource compilations and includes work. I've tried both a straight-up
#include in my main RC, and a TEXTINCLUDE. I've also tried setting the
dialog's
RC file to be excluded in the project, and that does prevents the error,
but it
still doesn't work right because the dialog cannot see the other resources
(in
the resource editor).

I've messed around with this all day and my test project is getting pretty
messy, so even if I manage to get it working somehow, I don't think I'll
be able
to figure out what I did to get it to work. :o So I figured I'd ask, in
the
hopes that someone already knows how it can be done.

Thanks a lot.

--
Alec S.
news/alec->synetech/cjb/net