Corona Simulator under Windows Only Detects Keyboard When Simulating Android Device

Solar2D Win32 Desktop
#1

Hi as of 2015.2687, the Windows version of the Corona simulator only detects the ‘key’ event when simulating an Android device.  The OS X simulator however, always detects them.

I will gladly file a bug, but I’m hoping engineering can simply flip a flag or remove a check to allow all simulated devices on OS X and Windows to accept ‘key’ events?

I’m raising this point since, I do nearly 100% of my dev on Windows and I want to target the Windows desktop without having to use only certain simulator views while developing and testing.  (Especially when working on a universally targeted app).

Thanks,

Ed

#2

This is not a new feature, and has been around for ages.

iOS devices do not support key events. So when we simulate it, we don’t offer key events. If there’s a bug, it’s on the OS X side of things, where key events are improperly sent.

We plan on adding a way to simulate the desktop apps more easily than constantly rebuilding. Until then, you can simulate Windows Phone or Android to enable key events.

You can also use the little-advertised Corona Shell application in your Windows installation instead of building, though that has its own troubles.

#3

@Michael,

Thanks.  Yes, I know it has been this way for a while, I merely meant that it was still true in 2015.2687.  I hoped was something that could be changed easily, but I know you guys are uber busy, and with more important/interesting stuff, so I’ll just have to get by with Android simulated devices and custom setups.

Tip for anyone reading: You can create your own simulator ‘view configurations’ and fake out the simulator by telling it, you’re simulating an Android device.  For example, I needed key input to facilitate a demo recording while using an iPad resolution device.  So, I merely made a file configured like the iPad, but flipped the right flags for ‘Android mode’, and I was off to the races.

Cheers,

Ed

#4

Oh, wow. I’m not even sure it’s related, but this post got me to investigate and discover that Win32 builds evaluated as “device”. I’ve been playing on and off with the shell since it was available and was always confused by that.

(I’m now relaxing several device-only checks on the thinking that input devices will become much more pervasive, but I guess I can tighten that up as needed.)

So, thanks, inadvertent or otherwise!  :slight_smile:

#5

This is not a new feature, and has been around for ages.

iOS devices do not support key events. So when we simulate it, we don’t offer key events. If there’s a bug, it’s on the OS X side of things, where key events are improperly sent.

We plan on adding a way to simulate the desktop apps more easily than constantly rebuilding. Until then, you can simulate Windows Phone or Android to enable key events.

You can also use the little-advertised Corona Shell application in your Windows installation instead of building, though that has its own troubles.

#6

@Michael,

Thanks.  Yes, I know it has been this way for a while, I merely meant that it was still true in 2015.2687.  I hoped was something that could be changed easily, but I know you guys are uber busy, and with more important/interesting stuff, so I’ll just have to get by with Android simulated devices and custom setups.

Tip for anyone reading: You can create your own simulator ‘view configurations’ and fake out the simulator by telling it, you’re simulating an Android device.  For example, I needed key input to facilitate a demo recording while using an iPad resolution device.  So, I merely made a file configured like the iPad, but flipped the right flags for ‘Android mode’, and I was off to the races.

Cheers,

Ed

#7

Oh, wow. I’m not even sure it’s related, but this post got me to investigate and discover that Win32 builds evaluated as “device”. I’ve been playing on and off with the shell since it was available and was always confused by that.

(I’m now relaxing several device-only checks on the thinking that input devices will become much more pervasive, but I guess I can tighten that up as needed.)

So, thanks, inadvertent or otherwise!  :slight_smile: