At 11:14 AM -0700 2/15/02, Terry Dennis wrote: >re: This blurb from the "_news.txt" file ... > >* Allow read access to "attr" fields of Control, List, Bitmap, Label, > and Scrollbar objects if the "accessor" function is not available -- > FrmGlueGetObjectUsable accesses those fields. FrmGlueGetObjectUsable > also accesses Gadget and Table objects, but Poser already allows > read access to "attr" for those objects. [Catherine White] > >Does this mean that we WILL sooner or later be provided accessor routines >for the "attr" fields? Or, does it mean that it's now "safe" (legal?) to >access those attribute fields directly? If not, then this change might be >dangerous in that it will mask the "illegal" accesses to internal areas.
Direct access is allowed only so that FrmGlueGetObjectUsable can access those functions (or any similar wrapper code of your own). You application should not access those fields directly, but instead should go through the glue code and let it do it for you. The "accessor" function function alluded to in the note is actually a magic function available under PalmSim. The glue code knows about it and calls it when it's available. -- Keith Rollin -- Palm OS Emulator engineer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
