I would think that it would always be preferable to associate directly
with the object. I didn't recall the TableRowAttrType, off the top of
my head I only recalled the Draw callback receiving a table pointer but
no user provided argument.
The main point I was trying to make was that 'this' isn't magic, it is
structure pointer that is passed to your member function. Programmers
have to associate C++ 'objects' with OS 'objects' themselves.
I'd personally be hesitant to stash the object pointer in a row. It
seems that you would start ending up with special case handling for
scrolling and display, but I haven't worked it through.
Best Regards,
-jjf
-----Original Message-----
From: Roger Chaplin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 22, 2000 7:54 PM
To: Palm Developer Forum
Subject: RE: C++ Palm Apps (Teenee)
"Fitzpatrick, Joe" <[EMAIL PROTECTED]> wrote:
> I don't recall PalmOS Tables offering a user param, I seem to recall
> that they pass the table pointer in. In these instances you need to
> find a way to associate a particular OS object with your 'object'.
You
> could ask the OS to do it with something like the Feature Manager, but
> it would probably be a lot more effective to just keep your own linked
> list.
Well, the TableRowAttrType does have a UInt32 data element, that is
specifically designated as "for whatever the user wants" - that is, the
OS doesn't know or care what's there. Since each row has one of these,
you could have a different object associated with each row. Or, if
there's only one object associated with the table, why not put its this
into the 0th row's data?
--
Roger Chaplin
<[EMAIL PROTECTED]>
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
