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]]
Sent: Monday, June 28, 1999 18:21
To: '[EMAIL PROTECTED]'
Subject: CW resource editor symbol name choices
I'm going along creating my form, setting control
names w/ a prefix for control type (e.g. lstApps
for a list that will show apps), and I'm happy until
I take a look in the header file. Apparently CW
is not happy letting me choose my own names, it has
generated:
#define MainLstAppsList 1001
Apparently prepending "Main" (the name of the form
containing the lstApps list) and appending "List"
(the control type).
Am I going to have to adjust my own personal style
of coding by dropping my own (long used) control type
identification scheme, or can I modify (or even disable)
this "helpful" behavior of CW?
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.
Or am I the only one that finds this behind-the-scenes
"help" disturbing? I can get used to it if I have
to, but really an ID should be an ID everywhere, right?
Shouldn't I at least have the option as to whether I
get "helped" this way or not?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
