At 10:16 PM -0800 12/12/99, Neil Rhodes wrote:
>FldSetText/FldSetTextHandle expects an unlocked handle, and then locks the
>handle you give it. Thus, if you try to call it twice for the same record
>(imagine, a record with two editable strings in it), the second call will
>fail, since the handle will already be locked).
I think the second call to MemHandleLock would succeed but there would be trouble
later. Each field thinks it can just unlock the handle and resize it when needed. But
the other field is contributing its own 1 to the lock count. So when either field
tries to resize the handle, it'll fail.
>Of course, two different fields editing the same record, each trying to
>resize it would cause problems.
Each field knows what portion of the chunk belongs to it. If the first field resizes
the handle, the second field's portion should change, but it won't know that.
You could imagine a system where the fields knew about each another so they could
collaborate better, but it would be complicated - not Zen of Palm.
-
Danny Epstein, Applied Thought Corporation
Have friends with Palm organizers? Get BeamBooks!
http://www.appliedthought.com/beambooks
