Textfield Properties Can't Be Set In Runtime Listener In Latest Build

Games
#1

Hello,

 

For some reason the latest build broke this code of mine:

 

    local search = native.newTextBox(0, 0, 70, 24)     search.text = searchLabel     search.isEditable = true     search.hasBackground = false     search.isVisible = false     search:addEventListener("userInput", searchF)          local function scene\_loaded()             print("Here", search)             if search then                 print("search", search.isVisible)                 search.isVisible = true                 print("search", search.isVisible)             end                  Runtime:removeEventListener("sceneLoaded", scene\_loaded)     end     Runtime:addEventListener("sceneLoaded", scene\_loaded)  

Inside the Runtime function I can not set the search field to isVisible true/false for some reason. The print statements show the correct values, and the last print statement shows that the isVisible value changes to true, yet the textfield doesn’t appear in the app. Also if I change the Runtime listener to a timer instead it works.

#2

Actually it seems to happen in build 1053 as well. Not in any of the builds before that though.

#3

I have the same bug in my code… I was troubleshooting it for hours last night. Seems that if you set the isVisible property to false on a textBox and try to set it to to true later on, the textBox doesn’t respond to the change. You can see the value changed via a print statement but the textBox remains invisible. I am happy I’m not the only one experiencing this, I thought I was going crazy for a minute.

#4

I’ll report this to the engineers.

#5

We are still looking into this.

#6

We need to you build a sample app that demos the problem and “Report a bug” (at the top of the page).  You’re submitted sample that shows the problem should not include any 3rd party libraries and as minimum of a code as you can to reproduce the error.

 

Thanks

Rob

#7

Thanks for the help. I’ll see if I can manage to file a bug report about it tomorrow night, thanks again.

#8

Actually it seems to happen in build 1053 as well. Not in any of the builds before that though.

#9

I have the same bug in my code… I was troubleshooting it for hours last night. Seems that if you set the isVisible property to false on a textBox and try to set it to to true later on, the textBox doesn’t respond to the change. You can see the value changed via a print statement but the textBox remains invisible. I am happy I’m not the only one experiencing this, I thought I was going crazy for a minute.

#10

I’ll report this to the engineers.

#11

We are still looking into this.

#12

We need to you build a sample app that demos the problem and “Report a bug” (at the top of the page).  You’re submitted sample that shows the problem should not include any 3rd party libraries and as minimum of a code as you can to reproduce the error.

 

Thanks

Rob

#13

Thanks for the help. I’ll see if I can manage to file a bug report about it tomorrow night, thanks again.

#14

Any news on this?

Edit: Noticed it only happens when using director class. Perhaps there’s a bigger underlying issue causing this?

#15

Any news on this?

Edit: Noticed it only happens when using director class. Perhaps there’s a bigger underlying issue causing this?

#16

Bumping this again, any news?

Edit: It’s still occurring in the latest daily

#17

Did you ever file a bug report?  What is the bug ID #

#18

Yeah, #22569

#19

Director is not a Corona Labs product.  I just noticed that in the ticket and above after I asked you to submit the ticket.  Since Director isn’t something we support and it’s only happening when using Director, I would recommend that you look through the director code and see if it’s in any way interfering with the native library or your code.

I know this occurred with a daily build at some point, and it’s possible that Director hasn’t been updated due to changes and that it needs updated.

#20

Hey, @Mitaten try build 1082.  There was this little nugget in the release notes today:

Mac, iOS - fixed implementation of “hasBackground” for TextFields

 

I don’t know if that will solve your problem or not, but it’s worth a look.