There's nothing like trying this out first hand. About a year ago I picked up a touch screen monitor for my Win8 laptop (non-touch at the time) and started playing around with this.

The good news is that most things just work with touch pointing in VFP apps. VFP has more quirks than other applications - there's a bit of lag for clicks (you need to linger a little longer on buttons for clicks to take for example). Some activeX controls are worse yet - I use ActiveBar for most of my VFP desktop apps and that has quite a bit of delay or some times requires multiple clicks.

Other issues I ran into: Popup keyboard popup is not consistent in VFP apps - it doesn't pop up automatically you have to manually pull the keybord from the task tray. There might be a Windows Message to force that automatically though with some API programming.

+++ Rick ---

>Have been asked on the effort to make an existing app usable on Win8 touch devices, so I remembered this thread, as I have not tried anything with Win-Touch devices yet. Answers to the questions inline appreciated
>
>
>>2-All of menus should be created with push buttons too.
>
>"should be" as in "won't work on touch otherwise" or "better use large push buttons, or handling will be a PITA"?
>
>>3-Create your own onscreen keyboard, don't use Microsoft's one.
>
>same as above: necessary groundwork before any prototype port can be used with vfp as something barfs when using MS keyboard with vfp app (focus events?) or can I use MS keyboard with my vfp app together until I have a signed contract including budget for a vfp keyboard ?
>
>>4-Do not use combobox and native spinner control.
>
>App uses lots of comboboxes - first idea from handling of comboboxes on Android would be to create a class - similar to some date field entries, where a calendar pops up - where a new form with all options available in dropped-down state is offered on drop-down event, so a previous standardization on rowsourcetypes used in the app might help cut down on testing all devices. Any problems with the approach ? Working code somewhere I can reuse and build upon ? API call which I can use to tell my app to work in "touch mode"?
>
>>Create your own spinner control with big push buttons + textboxes.
>>5-Do not use date type and numeric type values for textbox controls. Use string and convert strings date-string-date, numbers num-string-num.
>
>similar to 2 and 3: generic classes plus quite a bit of fiddling with class hierarchy would be necessary - nothing impossible, but would a prototype still using the old/generic stuff be totally unusable (like no entry possible and field having !empty()-validation rules) or just hard to handle until better solution similar to 4 is finished and integrated in the app hierarchy ?
>
>I will look over the existing code to get a clear picture on needed clean-up effort, getting a touch device is not that far out, but expanding a lot of effort to create prototypes to demo/check handling in vfp is risky at the discussion state, as the job might never happen (or lead to a reduced budget, as stuff too-well-done-previously clearly can be reused). Any futher links to code for vfp ?
>
>tia
>
>thomas