On Oct 3, 2010, at 2:27 PM, Walter Lenk wrote:

> 
> I am having a problem with how text is vertically justified in an edit field - it seem's the same code justifies differently when running under OS 10.6 than it does when running under OS 10.5.
> 
> I am using this code to generate the edit fields:
>    EDIT FIELD  Ef%, "", @Rect1, _FramedNoCr, _LeftJust

Sorry Walter. I don’t have a 10.6 and 10.5 machine to experiment but here is my editorial on this topic:

The FB runtime( FBAppearanceButton() within AppThings.c in this case ) essentially ( with some defaults from its caller FBEditField() within EditFields.c  treating several field types the same ) passes the EDIT FIELD parameters to the legacy Carbon call CreateEditUnicodeTextControl(), so there is reduced opportunity for FB to hose things. Have you tried creating the edit field in a nib and comparing the 10.6/10.5 results?  Even though virtually all UIs can be created programmatically ( same is true for Cocoa nibs ), Apple expects developers to create UIs in a nib and that is where they put their efforts. Apple has been ignoring Carbon for several years now, so any bugs won’t be fixed.  Also, you’ve undoubtedly noticed the FBtoC documentation shows EDIT FIELD as only partially implemented. Using a nib does not have these limitations.

One more thought: time permitting, building a new app is a good time to switch to Cocoa.

To recap: if using FB use Carbon nibs. 



Brian S