just posting here so in the future if anyone looking to do the same thing
use this in place of native text fields.
You 2 are now acting more like gentlemen, thanks.
The Apple article makes sense, they are out to make money and I appreciate that, its the American way!. I did some other research and found that indeed other SDK companies are saying the same thing(ya sure you can), but in fact no you can’t 
I don’t understand they are all are getting away with fraudulent claims but that is another matter I guess.
I can continue to learn Corona and lua and when I am ready for real testing, go with the MacInCloud.com to do finaly testing and fixes before submitting to iTunes. It’s late and got paged on our servers tonight so I will have to make sure to reread that apply policy article to make sure I got a full comprehension on Apples rules.
Gib
Sounds like you’ve got some stuff sorted out, but let me answer the “Why can’t I don’t native.textFields in the Windows Simulator?” question.
A. Blame Microsoft. But since that answer doesn’t say way, here’s the issue. On Microsoft Windows, you cannot mix native display objects, like text fields, with OpenGL canvases. Corona SDK is an OpenGL application. That’s how we get the graphics performance we do. Apple’s OS-X and iOS as well as Android permit native objects and OpenGL canvases can co-exist (though you cannot put native objects inside of OpenGL constructions like displayGroups.
There are a couple of routes… one, the seemingly painful one is to simply build as much of your app as you can that doesn’t involve keyboard input and if you need the input, you can just hard-code the text while testing. Then when you need to work out the kinks of the input system, then build for device. You will find there are quite a few things that have to be tested on device, like Facebook, Ads, inApp Purchases, GameNetwork, etc. We all love the speed of the simulator but at the end of the day, some things simply need to be done on the Simulator.
The other options is to build your own keyboard. I did this for a client and while I didn’t support every character and shift-states, it was all done in an OpenGL friendly way so I could test it in the Sim. It’s a lot of work. Windows also supports the new key events and can be used to capture the Windows keyboard, so building your own is a real possibility.
I want the simulator can show input dialog after click native textfield.
Like you show native.showAlert() as normal windows message box. :wub:
native.showAlert() is an object that exists outside the bounds of your app. It’s put there by the operating system usually. For the actual app, where you would want the text field to be part of the app itself, then we get into the Microsoft not letting native objects work in OpenGL apps. In the Microsoft world, they want everyone to use DirectX and not OpenGL so things you might see other Windows apps do, its because DirectX is a bit more tightly integrated on that platform. Since we are building for iOS and Android, OpenGL is the cross-platform high speed graphics engine of choice.
Believe me, we would love to give Windows users this feature.
I want the simulator can show input dialog after click native textfield.
Like you show native.showAlert() as normal windows message box. :wub:
native.showAlert() is an object that exists outside the bounds of your app. It’s put there by the operating system usually. For the actual app, where you would want the text field to be part of the app itself, then we get into the Microsoft not letting native objects work in OpenGL apps. In the Microsoft world, they want everyone to use DirectX and not OpenGL so things you might see other Windows apps do, its because DirectX is a bit more tightly integrated on that platform. Since we are building for iOS and Android, OpenGL is the cross-platform high speed graphics engine of choice.
Believe me, we would love to give Windows users this feature.