TextInput large string rendering issues

[illright]

During my app tests, I've noticed something very strange. The multiline TextInput renders text as usual, but when I add more text to a single line than some fixed size, the entire line becomes a black strip. In my test I've used the letter "M" 630 times and 631st is messing up the text. As for other letters, it takes more of them, but the same glitch occurs. Screenshot provided.

[KeyWeeUsr]

I had similar problem, on pc and on android. On android it was much lower amount of characters. I think it may depend on the Texture max size in OpenGL that you can see when your app starts.

[kived]

Completely black or white textures like this are generally indicative of either exceeding the Texture max size, or running out of VRAM for the GPU. Likely the former in this case, as @KeyWeeUsr noted.

[KeyWeeUsr]

Isn't there some warning directly in OpenGL that could be redirected into console? Then a user could catch when either max size or VRAM is not enough. It'd be nice, like that warning with max iterations in Clock.

[akshayaurora]

The correct solution here is to get TextInput to make sure long textures
are not used, the view pane is not big and maybe we could look at trying to
make sure only certain more chars than in the view window are
rendered...Just like we do for text vertically(lines)...

On Mon, Apr 11, 2016 at 8:55 PM, Peter Badida notifications@github.com
wrote:

Isn't there some warning diretly in OpenGL that could be redirected into
console? Then a user could catch when either max size or VRAM is not
enough. It'd be nice, like that warning with max iterations in Clock.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#4166 (comment)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.