On Jan 30, 2009, at 12:46PM, Brian Slick wrote:
It starts to occur to me that I don't actually want an instance, I
want the real deal.
On Jan 31, 2009, at 9:31AM, Brian Slick wrote:
It may be a nonsensical statement here (good to know), but in the 3D
CAD world that I'm used to, which I hav
On Jan 31, 2009, at 10:31 AM, Brian Slick wrote:
And I believe that I do understand the difference between objects
and pointers (I could be mistaken). The part I'm missing is what
this needs to look like in code. I'm afraid I need some handholding
here. If I knew what I needed to do in o
On Jan 30, 2009, at 9:47 PM, Ken Thomases wrote:
On Jan 30, 2009, at 2:46 PM, Brian Slick wrote:
It starts to occur to me that I don't actually want an instance, I
want the real deal.
That statement is nonsensical. There is no "real deal". An
instance is real. It's not some pale refl
Sorry I misunderstood the question then :) Just a newbie trying to
lend a hand where I can. Thanks for correcting me.
Joseph Crawford
On Jan 30, 2009, at 9:47 PM, Ken Thomases wrote:
On Jan 30, 2009, at 1:51 PM, Joseph Crawford wrote:
Why don't you create a base controller that those 2 co
On Jan 30, 2009, at 1:51 PM, Joseph Crawford wrote:
Why don't you create a base controller that those 2 controllers
subclass, that way they would inherit the functionality of reading
those properties, also they would inherit the methods for getting,
setting, etc.
BaseController
-- Control
Why don't you create a base controller that those 2 controllers
subclass, that way they would inherit the functionality of reading
those properties, also they would inherit the methods for getting,
setting, etc.
BaseController
-- Controller 1
-- Controller 2
in Base controller define those
