Printable View
There is a problem with the String Object and word wrapping. If you get a string of characters at just the right length, it will wrap punctuation marks without the word before them! Example:
https://drive.google.com/uc?export=d...jJCUlZJZjZzcWM
The sentence should wrap like this:
-------------------------- ii
oooo,
So what's wrong with the wrappin in the picture?
Ah darn, I was really hoping the ASO would be a solution here.
Okay I've posted it to the Bug Tracker here:
Bug/Issue Report #1933
Hi, if any Clickteam engineers see this thread, is this bug going to be getting your attention any time soon? It's getting tiring watching my strings show up like so (the issue is circled in red):
Attachment 15639
Wrapping depends on width&height of string object. If you set corret size then you get your goal.
I don't think you understand the problem. This is what correctly wrapping text should look like:
________
This text wraps correctly,
see what I mean?
--------------
And this is what is happening:
________
This text wraps wrong
, see the comma there?
--------------
Get it?
It's work for me like that:
________
This text wraps correctly,
see what I mean?
--------------
Maybe Windows verion issue?
If the text box is just the right width, it messes up the wrapping.
I've been having this exact problem, with punctuation not wrapping properly, but I guess there is no solution for it yet, which is surprising since this thread is almost a year old. Using Active System Box doesn't fix it either.
How did you managed to make the String object wrap text in the first place during runtime?
Did you just use Align Vertical = Center ?
I did test it with aligning the text vertically to center, and the comma does appear on the new line when it wraps. However, editing the text in the frame editor does not wrap the comma to the next line.
I've just began manually creating text animations in an active object. My RPG has lots of text and I hated how the punctuation was wrapping. Doing this is pesky but I get to control how it wraps.
I cant see this issue in the Bug Tracker ( maybe im just searching it wrong ).
Posting this issue there would make it more likely to be resolved/ fixed if applicable.