Hello List,
Normally variable names don't interfere with method names. So I can write:
CGFloat alphaValue = [ myCustomView alphaValue ];
Now, in an app the -drawRect: method of my custom view was not called although
it should. I found out that the culprit was an outlet named alphaValue which
On Sat, Jun 12, 2010 at 2:11 PM, Jochen Moeller jo.moel...@online.de wrote:
Hello List,
Normally variable names don't interfere with method names. So I can write:
Strictly speaking, Variable names can never interfere with method
names. The compiler determines the type it needs from context,
Am 12.06.2010 um 23:22 schrieb Kyle Sluder:
On Sat, Jun 12, 2010 at 2:11 PM, Jochen Moeller jo.moel...@online.de wrote:
Normally variable names don't interfere with method names.
Strictly speaking, Variable names can never interfere with method
names. The compiler determines the type it
On Sat, Jun 12, 2010 at 3:08 PM, Jochen Moeller jo.moel...@online.de wrote:
Kyle, thanks for the insight. Renaming the outlet was also my solution.
Does that mean that an outlet can be invalidated by a future version of a
class which introduces a new method with accidentally the same name?
