🚀 go-pugleaf

Thanks for the shortcut. There seems to be so many different ways to 
accomplish (nearly) the same thing that many solutions are often 
overlooked inadvertently.

So, I guess my question boils down to the GUI object that I'm using for 
display to the user and the interpretation of '\n' of that object. If 
I'm using a TMemo, then the '\n' is not interpreted as a EOL char, but 
rather it is displayed as \n. Ideally, I'd like to have that char 
interpreted as an EOL, or find an alternative.

For example, I'd like to send an AnsiString like the following....

AnsiString TextString = "1. Go to start.\n2. Walk north, 3 steps.\n3. 
Walk east, 5 steps.\n4. Dig up treasure.";

And I'd like that text to appear in my GUI as :

1. Go to start.
2. Walk north, 3 steps.
3. Walk east, 5 steps.
4. Dig up treasure.

Does this make sense? Is this possible, or do I have to create my own 
parser?

Thanks so much!

Rob


Remy Lebeau (TeamB) wrote:
> "Robert G. Hoover" <not.a.real.address@anywhere.sorry> wrote in message
> news:42826ce0@newsgroups.borland.com...
> 
> 
>>Is is possible to feed an AnsiString into a TMemo->Lines
>>and hardcode linefeeds?
> 
> 
> Yes, for example:
> 
>     void __fastcall THintForm::DisplayHint(TObject *Sender)
>     {
>         HintMemo->Lines->Text = GetLongHint(Application->Hint);
>     }
> 
> 
> Gambit
> 
>