For instance, if you have say,
Code: Select all
mary had a little lamb
If on the other hand, you have
Code: Select all
maryhadalittlelamb
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
Code: Select all
mary had a little lamb
Code: Select all
maryhadalittlelamb
That is correct, so you need at least one SPACE to get your text wrapped.The dontWrap on a field only handles word chunks, not character level text, is that correct?
Yah, I can believe it. I was a bit surprised that this was the default behavior, but probably shouldn't have beendunbarx wrote: ↑Sat Feb 16, 2019 5:57 pmThis has been a subject of discussion forever, that a space, and not simply the width of a field, determines wrapping. There are a bunch of kluges using the formattedWidth, formattedText and actual text properties to be able to force line wrapping in unspaced text.
Well, like everything, there are the 'exceptions to the rule...', and this case is no different. Inspired by one of your posts to more fully explore creating text editors, I was testing opening different files. In this case, the file had an extremely long URL in it, which of course has no spaces, but is certainly readable and may even be desirable to read.FourthWorld wrote: ↑Sat Feb 16, 2019 9:37 pmSo the issue tends to come up when displaying things that aren't readable text, which raises the question: if it's not for reading, why bother putting it into a field?
I would, if I thought it needed enhancing. Once you know what triggers what, though, it is handled easily enoughFourthWorld wrote: ↑Sun Feb 17, 2019 7:32 pmIt may be good to include that in the enhancement request.
How's the rest of your text editor coming along?