Using Win32 functions in Visual FoxPro Image Gallery
Code examples:
Accessing examples contained in this reference from a VFP application
Enumerating the subkeys of a user-specific key
GDI+: Color Transparency
How to display a user-defined icon in the MessageBox dialog
Memory usage info for current VFP session (WinNT only)
Obtaining heap handles and enumerating memory blocks for the current VFP session (WinNT only)
Obtaining the bounding rectangle for the specified device context
Printing text on the client area of the main VFP window
Reading the state of mouse buttons within DO WHILE loop
Retrieveing general information about the driver and data source associated with an ODBC connection
Semi-transparent Form
Setting the mouse capture to the specified window
Tracking mouse movement to detect when to start dragging
Using the GetTempFileName
Using the SystemParametersInfo function
Using vendor-neutral SQL constructs
Winsock: creating a socket that is bound to a specific service provider
Changing pitch and speed of a wave file
Connecting a local device to a network resource
Copying strings through the global memory block
Creating a directory on the FTP
Displaying animated images on FoxPro form with BitBlt and StretchBlt functions
Displaying standard progress dialog box when copying files
Dragging files from Explorer window and dropping them on FoxPro control (requires VFP9)
How to display Windows On-Screen Keyboard

User rating: 7.5/10 (4 votes)
Rate this code sample:
  • ~
More code examples    Listed functions    Add comment     W32 Constants      Translate this page Printer friendly version of this code sample
Versions:
click to open
Before you begin:

For data entry, instead of relying on the physical keyboard, user may choose using Windows On-Screen Keyboard instead. This virtual keyboard gives access to all standard keys.

On-Screen Keyboard executable file, osk.exe, resides in System32 directory. Note that on 64-bit systems this file cannot be launched from 32-bit process. "File System Redirector" article on MSDN explains why:
32-bit applications can access the native system directory by substituting %windir%\Sysnative for %windir%\System32. WOW64 recognizes Sysnative as a special alias used to indicate that the file system should not redirect the access.
#DEFINE MAX_PATH 260
#DEFINE OSK_EXE "osk.exe"

DO declare
= ShellExecute(0, "open", GetOskPath(), "", "", 1)
* end of main

FUNCTION GetOskPath() As String
    LOCAL cPath

    cPath = PathCombine(;
        GETENV("windir"),;
        "sysnative",;
        OSK_EXE )

    IF FILE(cPath)
        RETURN m.cPath
    ENDIF

    cPath = PathCombine(;
        GetSysDir(),;
        OSK_EXE )

RETURN IIF(FILE(cPath), m.cPath, OSK_EXE)

FUNCTION GetSysDir
    LOCAL cBuffer, nBufsize
    cBuffer=REPLICATE(CHR(0), MAX_PATH)
    nBufsize= GetSystemDirectory(@cBuffer, LEN(cBuffer)) 
RETURN SUBSTR(cBuffer, 1, nBufsize)

FUNCTION PathCombine(p1, p2, p3, p4, p5) As String
    LOCAL cBuffer, cPath1, cPath2, nIndex, nCount
    nCount = PCOUNT()

    DO CASE
    CASE nCount = 0
        RETURN ""
    CASE nCount = 1
        RETURN p1
    ENDCASE

    cBuffer = m.p1

    FOR nIndex=2 TO nCount
        cPath1 = STRTRAN(m.cBuffer, CHR(0), "")
        cPath2 = EVALUATE("m.p" + TRANSFORM(m.nIndex))
        cBuffer = REPLICATE(CHR(0), MAX_PATH)
        PathCombineApi(@cBuffer, cPath1, cPath2)
    NEXT
RETURN STRTRAN(m.cBuffer, CHR(0), "")

PROCEDURE declare
    DECLARE INTEGER GetSystemDirectory IN kernel32;
        STRING @lpBuffer, INTEGER nSize

    DECLARE INTEGER ShellExecute IN shell32;
        INTEGER hWindow, STRING lpOperation,;
        STRING lpFile, STRING lpParameters,;
        STRING lpDirectory, INTEGER nShowCmd

    DECLARE INTEGER PathCombine IN shlwapi;
    AS PathCombineApi;
        STRING @lpszDest, STRING lpszDir,;
        STRING lpszFile

User rating: 7.5/10 (4 votes)
Rate this code sample:
  • ~
1457 bytes  
Created: 2012-02-18 22:46:23  
Modified: 2015-10-28 09:36:34  
Visits in 7 days: 71  
Listed functions:
GetSystemDirectory
PathCombine
ShellExecute
Printer friendly API declarations
My comment:

On-Screen Keyboard`s window class name is "OSKMainClass". Knowing this, a VFP application can test the visibility of the On-Screen Keyboard by calling the FindWindow. By calling the SetWindowPos or similar API function, the virtual keyboard can be shown, hidden, or positioned at a specified point on the screen.
Word Index links for this example:
Translate this page:
  Spanish    Portuguese    German    French    Italian  
FreeTranslation.com offers instant, free translations of text or web pages.
User Contributed Notes:
There are no notes on this subject.


Copyright 2001-2016 News2News, Inc. Before reproducing or distributing any data from this site please ask for an approval from its owner. Unless otherwise specified, this page is for your personal and non-commercial use. The information on this page is presented AS IS, meaning that you may use it at your own risk. Microsoft Visual FoxPro and Windows are trade marks of Microsoft Corp. All other trademarks are the property of their respective owners. 

Privacy policy
Credits: PHP (4.4.9), an HTML-embedded scripting language, MySQL (5.6.30), the Open Source standard SQL database, AceHTML Freeware Version 4, freeware HTML Editor of choice.   Hosted by Korax Online Inc.
Last Topics Visited (54.196.71.49)
2.8 min.Function: 'inet_ntoa'
Google
Advertise here!