K
K. Shier
Friend variables "are accessible from within the program that contains their
declaration and from anywhere else in the same assembly." according to the
VS.Net help. This sounds like a pretty broad scope!
So why, when attempting to inherit a form from a base form class, is
'Friend' inadequate to give inherited forms 'public'-style access to
inherited controls? I.E. - i have a base form with two group boxes on it.
When they are declared 'Friend', i can't drag and drop controls into them in
inherited forms in the visual form designer. When they are declared
'Protected Friend', they work as expected.
Getting back to the definition of Friend - isn't any inherited form within
the same project going to be considered "...within the program... [or] ...in
the same assembly."? By now, my empirical evidence indicates that this not
the case, but i am wondering WHY?!
TIA! =)
declaration and from anywhere else in the same assembly." according to the
VS.Net help. This sounds like a pretty broad scope!
So why, when attempting to inherit a form from a base form class, is
'Friend' inadequate to give inherited forms 'public'-style access to
inherited controls? I.E. - i have a base form with two group boxes on it.
When they are declared 'Friend', i can't drag and drop controls into them in
inherited forms in the visual form designer. When they are declared
'Protected Friend', they work as expected.
Getting back to the definition of Friend - isn't any inherited form within
the same project going to be considered "...within the program... [or] ...in
the same assembly."? By now, my empirical evidence indicates that this not
the case, but i am wondering WHY?!
TIA! =)