Problems with Simulator recognizing onKey listeners

Has anyone noticed the latest daily builds having a problem recognizing when a key is struck on the keyboard? Has this been going on for some time and I just didn’t know it? 

I’m using the test code straight from the API here and not getting any terminal printouts. Am I missing something?

UPDATE: forgot to post versions. This is occurring on every daily build I’ve tried since 2511.

It could be the “terminal printout problem” if the only problem is not seeing the prints.  We’ve added “Corona Terminal” back on the Mac which should be used if you’re not getting output your expecting in the terminal window we launch.

Rob

@Rob, thanks for the info. I mostly use Windows for active development (Le gasp!) and I haven’t had much success in seeing the print statements I was talking about. But… 

I just checked the logs on device and, lo and behold, we have print statements. I apologize, as I wasn’t aware of this “terminal problem” and every other print statement I have works. I’ll get back to work, have a great weekend!

Alex,

Key events definitely do work in the Corona Simulator for Windows.  I just re-tested it today to be sure.  But note that key events *only* work when running an Android or Windows Phone skin.  They will *not* work when running an iOS skin.  We did this on purpose because iOS devices do not support key events.  That is, we’ve set up the simulator to correctly simulate key events according to the device you are simulating.

Note:  The Mac version of the Corona Simulator is the only one that is mishandling key events.  It wrongly provides key events for the iOS skin and it provides the wrong key names for some keys, such as the space key.  At one point we had no support for key events on Mac (Windows got it first) and it was just a quick and dirty thing we added at the time to help Corona developers at the time.

Wish I didn’t start this thread because it’d be good for an FtF. Thanks for the tip Josh!

No reason you can’t use your own thread…

It could be the “terminal printout problem” if the only problem is not seeing the prints.  We’ve added “Corona Terminal” back on the Mac which should be used if you’re not getting output your expecting in the terminal window we launch.

Rob

@Rob, thanks for the info. I mostly use Windows for active development (Le gasp!) and I haven’t had much success in seeing the print statements I was talking about. But… 

I just checked the logs on device and, lo and behold, we have print statements. I apologize, as I wasn’t aware of this “terminal problem” and every other print statement I have works. I’ll get back to work, have a great weekend!

Alex,

Key events definitely do work in the Corona Simulator for Windows.  I just re-tested it today to be sure.  But note that key events *only* work when running an Android or Windows Phone skin.  They will *not* work when running an iOS skin.  We did this on purpose because iOS devices do not support key events.  That is, we’ve set up the simulator to correctly simulate key events according to the device you are simulating.

Note:  The Mac version of the Corona Simulator is the only one that is mishandling key events.  It wrongly provides key events for the iOS skin and it provides the wrong key names for some keys, such as the space key.  At one point we had no support for key events on Mac (Windows got it first) and it was just a quick and dirty thing we added at the time to help Corona developers at the time.

Wish I didn’t start this thread because it’d be good for an FtF. Thanks for the tip Josh!

No reason you can’t use your own thread…