FairyGUI RichText AutoSize is not working as expected

[iAbdulQadirKhan]

This works fine if RichText's AutoSize is None. If AutoSize is Height + Width then it doesn't work as expected.

Expected:

Actual:

FairyGUI Design:

[iAbdulQadirKhan]

In cocos2d-v3 it was working fine with AutoSize Height + Width but now it converts multilines text into single line.

[rh101]

You would have more luck receiving help if you post up a test project with the least amount of code to reproduce the issue.

[iAbdulQadirKhan]

I have created a component in fairyGUI. In this component I have a rich text. And I'm just showing this component in game.

<?xml version="1.0" encoding="utf-8"?>
<component size="2048,1152" designImageAlpha="35">
  <displayList>
    <richtext id="n55_xe4g" name="txt_01" xy="1002,546" pivot="0.5,0.5" anchor="true" size="1332,294" scale="0.8,0.8" touchable="false" font="ui://a0gz3e6xprke0" fontSize="12" color="#ffffff" align="center" vAlign="middle" text="Tap on a chip to select&#xA;a bet amount"/>
  </displayList>
</component>

[iAbdulQadirKhan]

I have changed the parser option from HTML to Normal. This change fixes the multilines problem but creates an alignment problem.

change:

result:

[rh101]

You stated that the functionality was working in cocos2d-x v3, so if that is the case, then why not run both a cocos2d-x v3 build and an Axmol build side-by-side, and step through the code that parses and formats the text? You could then figure out exactly where the differences in the output are. Strategic use of breakpoints would save you stepping through irrelevant sections code to save you time.

[iAbdulQadirKhan]

I have compared the richtext related code with the cocos2d-v3 but not find the solution of this problem.

[rh101]

Comparing the code is not enough. As I mentioned earlier, you need to run the code for both cocos2d-x v3 and Axmol, and step through through them with the debugger to find where the the output differs.

[iAbdulQadirKhan]

Sorry I was wrong. The alignment issue is also present in cocos2d-v3. The reason for the above change is that the html parser removes the escaped characters (\n) from the text string.