|Hi led mike,
My example was for a simple dialog. My situation, and I guess this is something many other programmers have to face, is that I have dialogs that already have a working class with all the code and variables and event handlers doing their stuff. Now, I am adding a copy for this same dialog to add features to it, so logically I will want to use the same code that is already there. The compile condition I add to the dialog copy makes it available only when I compile resources with this condition set. I can add code to the dialog that will also be conditionnaly compiled with the same condition. This makes adding new features to a dialog easy and also is more team friendly.
You are suggesting to add a completly new class to the dialog. This would involve copying all the source from the other class to this new class and then adjusting the class name to match the new. If a modification is done to the original dialogs code (team) it will not be reflected in this class.
Why a copy of a dialog resource would not be a good devcelopement approach ?
* google is your friend *