Character Image Object Bugs
The Character Image Object has some bugs. Newline is one of those things. When you insert a text into the Settings/Text field,and need two line breaks, then you need to add at least one spacebar that the second new line gets countet as a new line. Else the second line break gets ignored, and you just get one new line.
Same for setting the text via an expression. Two or more Newline$ counts as one. You need to insert a piece of empty text so that the Newline$ creates a new line then, like +" "+
Character Image Object does not work with scrolling frames. It stays invisible, and cannot be convinced to show its content. And from what some X/Y counters tells me, its position gets reset to 0/0 in the moment the frame scrolls. But as told, it is invisible anyways.
Last but not least, mobichan has reported this one here too:
Quote:
Not sure if this is the right place, but the Character Image extension "visble at start" seems to have a bug. If you have it unchecked, but also have a default string in the object's properties, the object is visible when you run your application (running the actual swf only, not in debug).
Re: Character Image Object Bugs
I wanted to implement two languages. So i need to change the text. Setting the text via expression ended in a "expression too complex" message. Setting the text to the content of a string just worked once. The second try did nothing. I had to introduce a second Character Image Object. And now i simply toggle the visibility.
German Umlauts (Ä,Ö,Ü) doesn`t get displayed.
Re: Character Image Object Bugs
Ah, no, doesn`t work neither with making invisible. It ignores the invisible setting.
Re: Character Image Object Bugs
Character Image seems to be not really compatible with HWA. A Frame that has around 0-1% processor useage in a normal standalone version has around 50% processor useage in a HWA version.