display.newText multiple lines text wrap cuts off words

We have a display.newText set with a certain width and 0 for the height, and the text automatically wraps as it should, but on several lines a portion of the last letter gets cut off.

So it looks like this:

Sarah and Tracy walked to a neighborhood

pond to look for tadpoles. Tracy carried a red  (the vertical line at the end of the ‘d’ is cut off, just looks like a c)

bucket and a net because she wanted to take (the right side of the ‘e’ is cut off)

some home. Sarah didn’t think they should

take the tadpoles. She had read that

tadpoles grow best in their natural

environment. In the pond, tadpoles have

food, shelter, and a place to crawl out when

they grow into frogs.

So in this example, two of the nine lines have the last letter cut off.

The width we are setting seems to be just after the word “when” in line 8.

As you can see, the end of the word “red” in line 2 and “take” in line 3 extends past that width cut off.

If the app doesn’t have room to fit these words without cutting them off, it should enact the text wrap and move those words down to the start of the next line, but it instead is cutting off the ends of the words.

This wasn’t happening when we were using build 1076, but is happening on 2100 and some of the other newer builds like 1259 and 1260.

This is happening regardless of the text and regardless of the width we set.

If we set a longer width, then the text wrap happens further in the line, but still several lines get the last letter cut off.

Any ideas?  Did I explain this so it makes sense?

Any help would be greatly appreciated - thanks!

This was happening on the simulator… but on an HDX 7" device it is taking those words that are cut off in the simulator and moving them down to the next line.

** MAY BE WORTH FIXING THIS SO SIMULATOR ACTS LIKE THE DEVICE **

Marking this as solved now.   =)

This was happening on the simulator… but on an HDX 7" device it is taking those words that are cut off in the simulator and moving them down to the next line.

** MAY BE WORTH FIXING THIS SO SIMULATOR ACTS LIKE THE DEVICE **

Marking this as solved now.   =)