As I said, I can see the method in their madness,
and I can even adapt if need be. But I think that
it is rather high-handed of them in a "we know what
is best for you" kind of way to do this.
Consider this: if I have an OK button on each of
a half dozen forms (for which I carefully use the
same id), I'll end up with
#define FormAOKButton 1001
#define FormBOKButton 1001
#define FormCOKButton 1001
...
when all I really wanted was
#define btnOK 1001
and all my code could be written using that
one symbol consistantly throughout.
Of course I can go back and write my own
#defines for the IDs, but I thought that
was what the GUI was doing for me when I
entered the symbolic name in the property
inspector. Instead it was just taking that
name as a starting point.
As I said, I can adapt if I have to, but
I'd rather have a tool that works the way
I want it to than one to which I have to
adjust. The ability to disable this "smart"
naming help would be nice. The property
of consistancy is one in which I place
great store: xyzzy should be xyzzy everywhere.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: William F. Weiher III [mailto:[EMAIL PROTECTED]]
>
> I also found this confusing at first, but once I knew it was
> happening, I
> found it quite convenient. I can use identical names for
> fields, labels, and
> controls in multiple forms and constructor makes them unique
> for me. You can
> always add
> #define LstApps MainLstAppsList if you really want to use
> your own names
>
> -----Original Message-----
> From: Richard Hartman [mailto:[EMAIL PROTECTED]]
>
...
>
> Basically -- I believe that if a symbol is "xyzzy"
> somewhere, it should be "xyzzy" everywhere ... I do
> not think that clarity is helped by having something
> be "xyzzy" one place and "MungedXyzzyPlonk" somewhere
> else.
...
