What LC or OS incantation do I use to involve the onscreen keyboard on a Win 10 tablet?

[David V Glasgow]

Thanks, Richmond, but as far as I can establish there is no way of detecting whether there is a physical keyboard attached to a Windows detachable keyboard device.  Quite a few Win programmers have discussed the issue, but no reliable solutions posted.

So I have come up with something that seems to work, and I would appreciate any predictable fail scenarios.

My app has a brief set up screen - select from pop up, select radio button, click start.  If that is achieved and is associated with > n mousemove messages, I’m assuming a mouse/trackpad is present, and therefore we are not running as a tablet, (either in tablet mode, or Win 10 touch screen without tablet mode).  I can then enable tooltips and not invoke an onscreen keyboard.  (and vice versa)

I think I’d have to wait a while before the Glasgow Tartan appears in Aldi - but if it does…..

Best wishes,

David Glasgow

> On 19 Mar 2018, at 12:33 pm, Richmond via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> I thought my buying USB Microscopes in LIDL was an all-time low . . .
> 
> Mind you, a friend of mine bought a kilt there.
> 
> 
> On 19.03.2018 13:27, David V Glasgow via use-livecode wrote:
>> Colleagues in Livecode,
>> 
>> I just purchased a Win 10 ‘convertible’ tablet from Lidl <https://www.lidl.de/de/trekstor-surftab-twin-10-1/p255395> solely for quick Win testing LC.  The upside is that it is astonishing value for money (£169).
>> 
>> The downside is that the on screen keyboard isn’t automatically invoked when no keyboard is attached and the cursor enters a field.  I can access the KB from the task bar, but who wants to do that all the time?  It also doesn’t seem to move things about to avoid the KB overlaying the field in question.
> 
> Right click (hold and release) in the textField, and select show touch keyboard icon.
> 
> Fairly inconvenient!
> 
> Here's some horrible Visual BASIC:
> 
> Sub Keyboard()
> On Error GoTo ErrorHandler
> 
> Call ShellEx("C:\Program Files\Common Files\Microsoft Shared\ink\TabTip.exe")
> 
> ProcedureExit:
> Exit Sub
> 
> ErrorHandler:
> MsgBox "Error" & ": " & Err.Number & vbCrLf & "Description: " _
> & Err.Description, vbExclamation, "Module1.Keyboard"
> Resume ProcedureExit
> 
> End Sub
> 
> https://borncity.com/win/2015/08/24/windows10-upgrade-on-screen-keyboardtouchscreen-fix/
>> 
>> I have seen a few complaints online that seem to suggest that this is how it works in Win 10.  I have a hard time believing that because it is so spectacularly stupid and irritating.
> I don't, frankly.
> 
>> Some apps seem to have worked around this problem, and I hope that someone on this list has also done so.
>> 
>> Any advice?  If I have to roll my own KB + field avoidance+ text entry system I will, but surely that shouldn’t be necessary?
>> 
>> Best wishes,
>> 
>> David Glasgow
>> 
>> _______________________________________________
>> 
> 
> Best of luck, Richmond.
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode