It was escaped in the second example. I think this is rare enough that we have bigger fish to fry even if it is a bug.
> On Jan 14, 2020, at 9:26 AM, Carlos Rovira <[email protected]> wrote: > > I don't think is a bug too. > If you want to translate to plain text you must escape it, or better make > whole in a var in AS3 and display the value. > > El lun., 13 ene. 2020 a las 18:46, Alex Harui (<[email protected]>) > escribió: > >> If I understand the scenario correctly, I don't think that's a bug. XML >> characters are translated into UTF-8 characters which are then parsed. The >> MXML Compiler is scanning all values for binding expressions. >> >> It would be a bug if there is no way to escape {} in a value so that it >> isn't seen as a binding expression. I honestly don't know if there is a >> way or not. I would check Flex documentation and use the Flex compiler to >> see if you can get {} to show up in a Flex label, then try the same syntax >> in Royale. >> >> My 2 cents, >> -Alex >> >> On 1/13/20, 4:31 AM, "Harbs" <[email protected]> wrote: >> >> I have the following markup: >> >> <sp:Code text='<sp:AssetList dataProvider="{provider}"/>' >> size="4" style="white-space:break-spaces;”/> >> >> I’m trying to display markup in the text property of a component. >> >> It shoould be displayed as: >> <sp:AssetList dataProvider="{provider}”/> >> >> But it’s displayed as: >> <sp:AssetList dataProvider="[object Object],[object Object],[object >> Object]”/> >> >> It looks to me like the Royale compiler is evaluating the brackets in >> the text. >> >> FWIW, I also tried: >> <sp:Code text='<sp:AssetList >> dataProvider="{provider}"/>' size="4" >> style="white-space:break-spaces;"/> >> >> and got the same result. >> >> I think this is a bug. Thoughts? >> >> Harbs >> >> > > -- > Carlos Rovira > http://about.me/carlosrovira
