hmm interesting - I wonder if this happens because its xml source sucked in (ie it escaped characters get parsed when it gets sucked it)

what happens if you have that sort of stuff inline as opposed to pulled in from a file?

just curious...

PBH

On 7/6/06, Jonathan Bezuidenhout <[EMAIL PROTECTED]> wrote:

Hi,

No nasty characters - just escaped ones.

It turns out that it is not that the string is too long - it is because it contains some escape sequences - it just happens to be that these strings are extra long.

Something like &lt;li&gt; makes it break - &amp; works though. Also, something like &#60; fails.  If you have something like &#13; in your XML the app cannot even compile.  All of these are perfectly good XML!

The above is using the <mx:XML source.../> construct where the XML is sucked in at compile time and the AS structure is created.

Jonathan


__._,_.___

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com





YAHOO! GROUPS LINKS




__,_._,___

Reply via email to