Joshua,
I’ve tested it on a stock Nook Color which I believe is a custom version of Android 2.2 (Nook settings says software version 1.4.3) and on a Samsung Galaxy Tab model SPH-P100 running “Firmware 2.3.4, Build number Gingerbread.EF17”
I have intentionally not upgraded the OS on the Galaxy Tab as I am under the impression that Corona supports this version of Android and I suspect many users don’t upgrade.
[import]uid: 9422 topic_id: 15794 reply_id: 129412[/import]
Stephen,
I just tried the code you posted up above with the newest daily build #942 on my Galaxy Nexus (Android 4.1 Jellybean) and it’s working. The text display object is showing a line break when I press the Enter key and your “added keystroke:” print statement is going off when I press the Enter key.
So, it sounds like this issue might by OS version or device specific. Can you tell me what make/model of your device is and the Android OS version it is running please? Thanks. [import]uid: 32256 topic_id: 15794 reply_id: 129396[/import]
Joshua,
I’ve tested it on a stock Nook Color which I believe is a custom version of Android 2.2 (Nook settings says software version 1.4.3) and on a Samsung Galaxy Tab model SPH-P100 running “Firmware 2.3.4, Build number Gingerbread.EF17”
I have intentionally not upgraded the OS on the Galaxy Tab as I am under the impression that Corona supports this version of Android and I suspect many users don’t upgrade.
[import]uid: 9422 topic_id: 15794 reply_id: 129412[/import]
Hi Joshua,
Were you able to try the test code on your Nook Color or Tablet? (Trying not to be a pest but I wanted to ping you before this issue fell off your radar)
-Stephen [import]uid: 9422 topic_id: 15794 reply_id: 129721[/import]
Hi Joshua,
Were you able to try the test code on your Nook Color or Tablet? (Trying not to be a pest but I wanted to ping you before this issue fell off your radar)
-Stephen [import]uid: 9422 topic_id: 15794 reply_id: 129721[/import]
Stephen,
I haven’t had time to test it on a Nook Color yet. I did take the time to add your bug report to my queue and note the 2 devices that this issue is happening on. There are others who have been waiting for bug fixes from me longer, so to be fair, I have to take care of them first. [import]uid: 32256 topic_id: 15794 reply_id: 129924[/import]
Stephen,
I haven’t had time to test it on a Nook Color yet. I did take the time to add your bug report to my queue and note the 2 devices that this issue is happening on. There are others who have been waiting for bug fixes from me longer, so to be fair, I have to take care of them first. [import]uid: 32256 topic_id: 15794 reply_id: 129924[/import]
Fair enough, thanks for whatever time you can spare on this issue.
It’s frustrating and nail biting to have to resort to begging for spare cycles from you over what is probably a one or two line code change. And I’m sure it’s no fun for you to have to juggle a long line of developers clamoring for your attention to their showstoppers. Is there a better way to handle things like this?
(Incidentally, something is still broken with the forum email alerts. I never saw you last reply in my inbox. EDIT: ok, I think I see a pattern. As soon as I posted this I got an email alert for the message you posted yesterday. And a few days ago I got a bunch of backed up email alerts for forum posts I’m subscribed to right after I posted something.) [import]uid: 9422 topic_id: 15794 reply_id: 130015[/import]
I’m sorry to keep you waiting on this issue. We’re trying our best to keep up with all of the issues, feature requests, and demands being thrown our way.
Since I don’t have time at the moment, I’m going to have someone here try to reproduce this issue on our other devices. Step one is to narrow down if this is a device specific or an OS version specific issue, which I’ll need to know in order to address it. We’ll keep you posted. [import]uid: 32256 topic_id: 15794 reply_id: 130036[/import]
Fair enough, thanks for whatever time you can spare on this issue.
It’s frustrating and nail biting to have to resort to begging for spare cycles from you over what is probably a one or two line code change. And I’m sure it’s no fun for you to have to juggle a long line of developers clamoring for your attention to their showstoppers. Is there a better way to handle things like this?
(Incidentally, something is still broken with the forum email alerts. I never saw you last reply in my inbox. EDIT: ok, I think I see a pattern. As soon as I posted this I got an email alert for the message you posted yesterday. And a few days ago I got a bunch of backed up email alerts for forum posts I’m subscribed to right after I posted something.) [import]uid: 9422 topic_id: 15794 reply_id: 130015[/import]
I’m sorry to keep you waiting on this issue. We’re trying our best to keep up with all of the issues, feature requests, and demands being thrown our way.
Since I don’t have time at the moment, I’m going to have someone here try to reproduce this issue on our other devices. Step one is to narrow down if this is a device specific or an OS version specific issue, which I’ll need to know in order to address it. We’ll keep you posted. [import]uid: 32256 topic_id: 15794 reply_id: 130036[/import]
Stephen,
Good news! I was able to successfully reproduce this issue on a Nook Color. The real issue here is that the TextBox listener would stop receiving events when you press the Enter key in a TextBox… and only on certain devices. The newline character is actually in the TextBox and can be retrieved correctly. This was just an event listener issue.
We’ve fixed the bug, but this bug fix will not be made available until 2 weeks from now. The reason is because we’re about to do a new release of our Corona SDK and this fix did not make it in in time. So, sorry about the wait. [import]uid: 32256 topic_id: 15794 reply_id: 130387[/import]
Stephen,
Good news! I was able to successfully reproduce this issue on a Nook Color. The real issue here is that the TextBox listener would stop receiving events when you press the Enter key in a TextBox… and only on certain devices. The newline character is actually in the TextBox and can be retrieved correctly. This was just an event listener issue.
We’ve fixed the bug, but this bug fix will not be made available until 2 weeks from now. The reason is because we’re about to do a new release of our Corona SDK and this fix did not make it in in time. So, sorry about the wait. [import]uid: 32256 topic_id: 15794 reply_id: 130387[/import]
Wow! That is great news! Thanks for tracking it down, Joshua.
Two weeks out is likely going to impact my release schedule plans, so who at Coronalabs can I bribe to sneak this into an earlier build? I have cash.
[import]uid: 9422 topic_id: 15794 reply_id: 130405[/import]
Wow! That is great news! Thanks for tracking it down, Joshua.
Two weeks out is likely going to impact my release schedule plans, so who at Coronalabs can I bribe to sneak this into an earlier build? I have cash.
[import]uid: 9422 topic_id: 15794 reply_id: 130405[/import]
Hi Stephen,
No bribes were necessary. 
It turned out we needed to do another round of debugging before the upcoming release and we decided to push this fix into it. I’m glad it’s working for you! Thanks for helping us isolate this issue. [import]uid: 32256 topic_id: 15794 reply_id: 131117[/import]
Hey, I guess the bribe worked! 
Thanks, Joshua, for getting the bug fixed and into the latest build. I just tested and it’s working great on Nook Color.
-Stephen [import]uid: 9422 topic_id: 15794 reply_id: 130895[/import]
Hi Stephen,
No bribes were necessary.
It turned out we needed to do another round of debugging before the upcoming release and we decided to push this fix into it. I’m glad it’s working for you! Thanks for helping us isolate this issue. [import]uid: 32256 topic_id: 15794 reply_id: 131117[/import]
Hey, I guess the bribe worked!
Thanks, Joshua, for getting the bug fixed and into the latest build. I just tested and it’s working great on Nook Color.
-Stephen [import]uid: 9422 topic_id: 15794 reply_id: 130895[/import]