Android device shows bad chars or black on textField when also using tabBar widget

Solar2D Daily Builds and Public Releases
#1

tabBar at the top, and some editable text in the middle. Everything is fine until it goes to sleep. On wake, text boxes are either blacked out, or the text is unreadable gibberish.

Only happens on the device.

Android tablet
Build: 846

What I did:
Started a new project using storyboards (since that’s what I’m doing in the app), and added pieces until the problem showed up. I then rolled back the last thing I added. It was the tabBar. All build settings etc are what I’m using in the full-on app.

Test project was added to the bug report I submitted. Throwing this in here too, just in case some other folks are seeing the issue in the wild.

[import]uid: 169520 topic_id: 30741 reply_id: 330741[/import]

#2

We’ve fixed this bug in the newest release version, build #894.

This issue actually has nothing to do with storyboard. This issue only occurs on Android 4.x devices with any native objects such as TextFields, TextBoxes, WebPopups, and WebViews… and it only happens when suspending/resuming your app. It turned out to be an OpenGL conflict with Google’s hardware accelerated native objects. In any case, it’s resolved in the newest version. [import]uid: 32256 topic_id: 30741 reply_id: 123164[/import]

#3

Awesome news. Thanks. And by the way, I was saying it was Widgets, not Storyboard (Just used that because that’s what I used in my app), but in any case, it’s good to hear it’s fixed. That’s the last piece of the puzzle for me.

[import]uid: 169520 topic_id: 30741 reply_id: 123167[/import]

#4

If you confirm that the newest release version fixes this issue, then that would be great! It should, but I just want to double-check and make sure that all Android 4.x graphics issues have been laid to rest. Thanks! [import]uid: 32256 topic_id: 30741 reply_id: 123328[/import]

#5

Indeed, I am not having jumbles or black issues any longer. However, text on a multiline textBox that’s say set to the height of the viewport will vertical align the text, but not other rendering abnormalities. Don’t know if that alignment issue is related or not. [import]uid: 169520 topic_id: 30741 reply_id: 123330[/import]

#6

I wasn’t aware of any TextBox alignment issues on Android. It’s supposed to aligned to the top-left corner by default. Are you saying it is centered vertically? [import]uid: 32256 topic_id: 30741 reply_id: 123344[/import]

#7

Right. It’s centered vertically. Here’s what I have:

 local inputText = native.newTextBox( 0, 0, display.contentWidth, display.contentHeight-50)  
 -- the - 50 is for a tabBar  
 inputText.font = native.newFont( native.systemFontBold, 12 )  
 inputText.text = "some text that's centered vertically"  
 inputText.isEditable = true  
 inputText:addEventListener('userInput', fieldHandler)

I don’t add it to a group, but it is part of a storyboard scene. Also, this only happens on my android device, and not in the mac sim. [import]uid: 169520 topic_id: 30741 reply_id: 123403[/import]

#8

Hey Joshua, should I make a separate bug ticket for this? [import]uid: 169520 topic_id: 30741 reply_id: 123543[/import]

#9

Sorry about the late response. I was really busy yesterday.

>> should I make a separate bug ticket for this?

Please do. You can do so by clicking the “Report a Bug” link at the top of this page. I recommend that you mention my name and this forum thread in the bug report to help expedite it. That way tech-support knows to hand it over to me immediately and it gets into my queue. Thanks! [import]uid: 32256 topic_id: 30741 reply_id: 123569[/import]

#10

We’ve fixed this bug in the newest release version, build #894.

This issue actually has nothing to do with storyboard. This issue only occurs on Android 4.x devices with any native objects such as TextFields, TextBoxes, WebPopups, and WebViews… and it only happens when suspending/resuming your app. It turned out to be an OpenGL conflict with Google’s hardware accelerated native objects. In any case, it’s resolved in the newest version. [import]uid: 32256 topic_id: 30741 reply_id: 123164[/import]

#11

Awesome news. Thanks. And by the way, I was saying it was Widgets, not Storyboard (Just used that because that’s what I used in my app), but in any case, it’s good to hear it’s fixed. That’s the last piece of the puzzle for me.

[import]uid: 169520 topic_id: 30741 reply_id: 123167[/import]

#12

This vertical alignment bug is now fixed. This fix will be made available in daily build #907, tomorrow. Thank you for bringing this issue to our attention. [import]uid: 32256 topic_id: 30741 reply_id: 123765[/import]

#13

If you confirm that the newest release version fixes this issue, then that would be great! It should, but I just want to double-check and make sure that all Android 4.x graphics issues have been laid to rest. Thanks! [import]uid: 32256 topic_id: 30741 reply_id: 123328[/import]

#14

Indeed, I am not having jumbles or black issues any longer. However, text on a multiline textBox that’s say set to the height of the viewport will vertical align the text, but not other rendering abnormalities. Don’t know if that alignment issue is related or not. [import]uid: 169520 topic_id: 30741 reply_id: 123330[/import]

#15

I wasn’t aware of any TextBox alignment issues on Android. It’s supposed to aligned to the top-left corner by default. Are you saying it is centered vertically? [import]uid: 32256 topic_id: 30741 reply_id: 123344[/import]

#16

Right. It’s centered vertically. Here’s what I have:

 local inputText = native.newTextBox( 0, 0, display.contentWidth, display.contentHeight-50)  
 -- the - 50 is for a tabBar  
 inputText.font = native.newFont( native.systemFontBold, 12 )  
 inputText.text = "some text that's centered vertically"  
 inputText.isEditable = true  
 inputText:addEventListener('userInput', fieldHandler)

I don’t add it to a group, but it is part of a storyboard scene. Also, this only happens on my android device, and not in the mac sim. [import]uid: 169520 topic_id: 30741 reply_id: 123403[/import]

#17

Hey Joshua, should I make a separate bug ticket for this? [import]uid: 169520 topic_id: 30741 reply_id: 123543[/import]

#18

Sorry about the late response. I was really busy yesterday.

>> should I make a separate bug ticket for this?

Please do. You can do so by clicking the “Report a Bug” link at the top of this page. I recommend that you mention my name and this forum thread in the bug report to help expedite it. That way tech-support knows to hand it over to me immediately and it gets into my queue. Thanks! [import]uid: 32256 topic_id: 30741 reply_id: 123569[/import]

#19

Thanks Joshua. Built and tested. Shows at the top left now as it should. However, the enter key no longer sends “submitted” for a multiline textbox. Is this on purpose? If so, how do I capture the enter key? I had it capturing before I updated to 907.
[import]uid: 169520 topic_id: 30741 reply_id: 124059[/import]

#20

Actually, it’s not sending several things. I may need to file another bug but I’ll run it past you and see what you think. Probably even need a new thread.

It now sends “editing” on the android mac sim. I only get ended and submitted when I click off somewhere. I thought, “Okay, I’ll use editing,”

BUT, it doesn’t send anything but “began” on the actual device. No more “editing”

I also tried to capture key presses using the “key” event, but it never captured anything. Very simple stuff with a Runtime: event listener sending to a handler that adds the event.keyName to the text of the field so I can see it in the device. All I get is “began” from my field handler (which I also have contact to the text field)… and that’s it. I need other events to be able to do anything useful.

Please advise. [import]uid: 169520 topic_id: 30741 reply_id: 124060[/import]