I know this is against the rules, but exactly how will I get into trouble if I use FldSetTextPtr(field,txt) where txt points to a string allocated temporarily off the stack? I follow it immediately with FldDrawField(field) and then exit the function, which deallocates the memory for the txt string. The field is non-editable. I know that if I ever call FldDrawField(field) explicitly again, it will problably blow up because the field has a pointer to unallocated and indetermiant memory. But I will never do that. Are there any implicit calls to FldDrawField, resulting from, say, another form that temporarily overlays the field in question? If this were Microsoft Windows (with which I am much more familiar), I know that windows are responsible for repainting themselves whenever an obscuring window goes away. But I gather that PalmOS does not work that way. It seems that PalmOS always saves the pixels before they are obscured, and restores them again when the obscuring form goes away. I really don't want to resort to dynamic string allocation unless I have to, so my question is, do I have to? I have tried it as I described above, and I can't seem to get into trouble.
Robert Scott, Ypsilanti, MI (reply through this forum, not by e-mailing me directly) -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
