Not sure if this is really a change, or just not noticed it before, but when I
assign the lines of a TMemo to a TStringList, I now have 0x0A characters at the end
of the lines.

procedure TfrmListEditor.GetText(xTextData : TStringList);
begin
   xTextData.Assign(editListDetail.Lines);
//    RemoveEmptyLines(xTextData);
end;

Hmm, having now sanitised this to remove the LF characters, I find that the .Text
value has no separators. Something odd is happening I think.

/Matthew Jones/

procedure TfrmListEditor.editListDetailChange(Sender: TObject);
begin
   lblCount.Caption := IntToStr(editListDetail.Lines.Count) + ' lines';
end;

This always shows "1 lines". Seems there's something broken in the memo. I'll raise
an issue with Tim for proper response.

/Matthew Jones/

Matthew,

<< Not sure if this is really a change, or just not noticed it before, but
when I assign the lines of a TMemo to a TStringList, I now have 0x0A
characters at the end of the lines. >>

I'm not seeing this here.  However, I am seeing an issue with the
TStrings.LineSeparator - it is set to CRLF and that is *not* working
properly and should be just plain LF.   I attempted in 1.03 to clean up the
rules regarding how line feeds are specified and interpreted, and this was
introduced then.  The JSON and compiled code always specifies < #32 in
Unicode format now in order to avoid any ambiguities between browsers in how
/r and /n are interpreted in string literals between IE and others.

Tim Young
Elevate Software
www.elevatesoft.com

Did you try my sample posted as an issue? and as comment to my note.

It sounds like you may have fixed it, but this simple code fails and is plainly
wrong.

procedure TfrmListEditor.editListDetailChange(Sender: TObject);
begin
   lblCount.Caption := IntToStr(editListDetail.Lines.Count) + ' lines';
end;


/Matthew Jones/

Matthew,

<< Did you try my sample posted as an issue? and as comment to my note. >>

Do you mean the line counts ?  If so, then yes, that's the same issue.

Tim Young
Elevate Software
www.elevatesoft.com

I've gone back to 1.02 until this is fixed - my app doesn't work well without this.

/Matthew Jones/

1.03b2 fixes the core string list.

There is another behaviour change in a component layout I have, but I've not looked
at that, so it could be anything including my bug.

/Matthew Jones/