TAdvMemo major issues

[Tesic_Zvonko]

Problem 1:

When TAdvMemo is using wordwrap mode:

AdvMemo1->WordWrap = wwClientWidth;

And long line is inserted which contains no spaces and wraps at the right edge:



When the text is copied to string via:

UnicodeString MyStr = AdvMemo1->Lines->Text;

The result is broken string with spaces introduced where the word wrap was present previously. In other words the string is damaged and no longer in original form. So the string might look like:

"longtextlongtextlo  ngtextlongtextlongtext  longtextlongtextlongtextlongtext longtextlon  gtextlongtext"

It should be continuous string and spaces should not happen. The same does not happen when the editor is not in wordwrap mode.

Problem 2:

The highlighter is not really smart and can't deal with broken HTML quotes and gives quotes priority over the HTML tags - that should be reversed. Example of UltraEdit shows how that should be handled instead.

Problem 3:

Resizing windows size can damage HTML tags and attributes beyond recognition due to introduction of spaces. The damaged attributes may contain URLs which no longer are working after this.

[brunofierens]

Problem1: get the text with AdvMemo.WrappedText:string;

Problem2: the < > characters have indeed priority. We'll investigate the pro's and con's of changing the priority.

Problem3: We'll investigate to fix this.

[Tesic_Zvonko]

Thank you - you don't have to investigate problem 3, after copying text from WrappedText property it no longer inserts unwanted spaces. Although it is completely illogical - why do you have 2 different properties for fetching text from the control - 

WrappedText if text is wrapped and Lines->Text if it is not...

[brunofierens]

In some cases it is desirable to have the text line by line as displayed wordwrapped in the memo, in other cases it is desirable to have the full text as is. That is the reason to provide the WrappedText and Lines.Text interface.