John,

Here is my post from a few weeks ago. It shows a static and an  
editable edit field. This could be done with a nib too.

One option is to use control-based edit fields and switch to modern  
EditUnicodeTextControls ( EUTCs )
'-------------------
include "Tlbx CarbonEvents.incl"

local fn BuildEUTCWnd
'~'1
dim as Str255                 s
dim as ControlFontStyleRec    tfs
dim as Rect                   r
dim as WindowAttributes       wa

wa = _kWindowCloseBoxAttribute¬
      _kWindowCollapseBoxAttribute¬
      _kWindowFullZoomAttribute¬
      _kWindowResizableAttribute¬
      _kWindowStandardHandlerAttribute

SetRect( r, 0, 0, 395, 219 )
appearance window -1, "EUTC", @r, _kDocumentWindowClass, wa
def SetWindowBackground( _kThemeActiveDialogBackgroundBrush, _zTrue )


SetRect( r, 98, 58, 304, 159 )
appearance button 1,,,,,, @r, _kControlEditUnicodeTextProc
def SetButtonTextString( 1, "Will hold more than 32k of text" )

SetRect( r, 186, 168, 256, 184 )
appearance button 2,,,,,, @r, _kControlStaticTextProc
def SetButtonTextString( 2, "Static Text" )


appearance window 1
end fn


fn BuildEUTCWnd


do
HandleEvents
until gFBQuit
'----------------

On Mar 25, 2008, at 8:01 PM, John Grimsley wrote:
> Brian,
>
> I did a search on Edit Fields (I believe), and got so many matches  
> for 2001 AD or earlier.
> Still fumbling my way around the FB list.
>
> Thanks,
>
> John G
>
>
>
> Brian Stevens wrote:
>>
>> On Mar 25, 2008, at 4:25 PM, John Grimsley wrote:
>>> My program relies on Edit Field and EDIT$ with various Fonts,  
>>> Sizes, Colors and Justifications (center, etc).
>>>
>>> What are the 'modern' replacements.  I'm all ears (Ross Perot).
>>
>> John - did you see the post earlier this month with the subject:  
>> "Roomy Edit fields" ? One of the posts ( maybe mine ) suggested  
>> EditUnicodeTextControls ( often referred to by their abbreviation  
>> EUTCs on this list ) as one possibility.
>>
>> However, there is no one size fits all answer because there are  
>> several good options. Common to all the options is no Quickdraw- 
>> based or old TextEdit-based calls. EUTC's work great in many  
>> situations but you might need Multi-Lingual-Text-Edit ( MLTE ).
>>
>> In order for the list to help you sort through the various  
>> options,  it would be best for you to describe how the edit fields  
>> are used and what kinds of functionality they need to support.  
>> This would include what the user needs ( i.e. spell check, data  
>> editing/filtering, double-byte character support ) but also what  
>> kind of processing you anticipate needing.
>>
>> Edit field and Edit$ are not fully supported in FBtoC, so those  
>> aren't the answer.
>>
>>
>> Brian S.
>>
>> -- 
>> To unsubscribe, send ANY message to: futurebasic- 
>> unsubscribe@...
>>
>
> --
> To unsubscribe, send ANY message to: futurebasic- 
> unsubscribe@...
>

Brian S.