General Macro Scheduler discussion
5 posts • Page 1 of 1
Code: Select all
OnEvent>key_down,VK1,0,srtStart Label>lblStart Wait>0.01 Goto>lblStart SRT>srtStart Dialog>Dialog1 object Dialog1: TForm Left = 317 Top = 198 HelpContext = 5000 BorderIcons = [biSystemMenu] Caption = 'Enter your password' ClientHeight = 113 ClientWidth = 340 Color = clBtnFace Font.Charset = DEFAULT_CHARSET Font.Color = clWindowText Font.Height = -11 Font.Name = 'MS Sans Serif' Font.Style =  OldCreateOrder = True ShowHint = True OnTaskBar = False PixelsPerInch = 96 Position = poScreenCenter TextHeight = 13 object Label1: TLabel Left = 272 Top = 24 Width = 32 Height = 13 Caption = 'VIEW' end object Edit1: TEdit Left = 39 Top = 15 Width = 218 Height = 21 PasswordChar = '*' TabOrder = 0 Text = 'PasswordChar is *' end object MSButton1: tMSButton Left = 133 Top = 78 Width = 75 Height = 25 Caption = 'Ok' TabOrder = 9 Default = True end end EndDialog>Dialog1 AddDialogHandler>Dialog1,MSButton1,OnClick,srtProcess AddDialogHandler>Dialog1,Label1,OnMouseDown,srtDisplayChars AddDialogHandler>Dialog1,Label1,OnMouseUp,srtHideChars AddDialogHandler>Dialog1,,OnClose,Quit Show>Dialog1, SRT>srtProcess GetDialogProperty>Dialog1,Edit1,Text,vPWStr MDL>vPWStr Exit>0 END>srtProcess SRT>srtDisplayChars SetDialogProperty>Dialog1,Edit1,PasswordChar,nullchar END>srtDisplayChars SRT>srtHideChars SetDialogProperty>Dialog1,Edit1,PasswordChar,* END>srtHideChars SRT>Quit Exit>0 END>Quit END>srtStart
Technically, since WaitKeyDown is a Macro Scheduler function and what I provided is an OnEvent function with a key_down parameter, the code is not for WaitKeyDown. In my testing, using a mouse click, the OnEvent worked reliably where the WaitKeyDown function did not.nodochau wrote:This code for WaitKeyDown.
In any case, I do not have a touch screen to test with. Used to have them and paid like $800 per monitor for 30 of them. Then when they started dying off we polled our users and found that of 90 people only 2 preferred the touchscreen over the mouse.
Searching the web for VK code and touchscreen I found only one reference that said a Windows CE touchscreen would produce a Virtual Code of 1 (one). Since VK1 is the Virtual Code for a mouse selection which is also essentially what happens when you touch a touchscreen I hoped the OnEvent would detect a VK1 when you touched your screen.
You can see ALL VK codes HERE. Try them all (There's only 254 of them). Or try the ones that might make sense. In the code I provided, you would substitute the number you want to try after the VK. So, OnEvent>key_down,VK1,0,srtStart would become OnEvent>key_down,VK235,0,srtStart or whatever number you want to test.
If none of the VK codes work, then I have one other possibility for you. Create a dialog that completely covers the screen. A touch on the dialog will certainly be detected. The dialog can be opaque or visibly transparent and will work either way. On detection of the touch, close the dialog and proceed with the rest of the script.