Hi,

no, that's strange, that shouldn't happen of course.

Thanks for reporting - I will check this!

Best regards,
Klaus

Hi,

an update to this - that's not directly a 'small' bug, it's more an 'incomplete' implementation of the text line-breaking algorithm.

As written for the WebGL textfields internally almost everything needs to be done manually - the browser itself provides only the raw text and the bounding boxes of the lines. So to get the final text as bitmap for a WebGL texture, it's necessary to map/fit and render the text into these boxes. This is done by trying word by word if the current word would still fit into the current bounding box - and if not, begin filling the next box with words.

And here was the incomplete implementation - the current algorithm was only considering white-space-characters as potential line-break possibilities, but there are also '-' characters within words where a line could break. Because this was missing the text rendering didn't match the bounding boxes anymore and the whole text gets wrong (resulting in something like 'cut of text' of other problems).

For the next release this had been fixed now, there the line-breaking algorithm has been much improved and should now match 1:1 the html rendering in (hopefully) all cases.

Best regards,
Klaus

Hi,

here now the fixed version:
krpano 1.19-pr9 / 1.19-pr10 / 1.19-pr11

Best regards,
Klaus