Using Win32 functions in Visual FoxPro Image Gallery
Code examples:
How to change display settings: screen resolution, screen refresh rate
Custom GDI+ class
Capturing keyboard activity of another application with the Raw Input API (VFP9)
How to display Windows On-Screen Keyboard
How to print a bitmap file
Using the LoadImage function to have a bitmap file loaded and displayed on VFP main window
Winsock: sending email messages (SMTP, port 25)
System Image List Viewer
Creating the Save dialog box to specify the drive, directory, and name of a file to save
The window and its ancestors
Custom HttpRequest class (WinHTTP)
Printing Image File, programmatically set print page orientation to landscape
Using Video Capture: displaying on FoxPro form frames and previewing video obtained from a digital camera
How to convert a bitmap file to monochrome format (1 bpp)
Mapping and disconnecting network drives
Custom FTP Class for Visual FoxPro application
Using EnumPrinters function to enumerate locally installed printers
Displaying the associated icons and descriptions for files and folders
How to activate Windows Calculator
How to download a file from the FTP server using FtpGetFile
Sending email messages with Simple MAPI
Confining Windows calculator inside the VFP main window
Windows Shell Icons displayed and exported to ICO files (Vista)
How to print FoxPro form
Retrieving Window Class information for the VFP window

User rating: 0/10 (0 votes)
Rate this code sample:
  • ~
More code examples    Listed functions    Add comment     W32 Constants      Translate this page Printer friendly version of this code sample
 
DO decl
 
LOCAL hWnd, lcClassName, hInstance, lcWndClass,;
    lcClassNameRet, lcMenuNameRet
 
STORE SPACE(250) TO lcClassNameRet, lcMenuNameRet
 
hWnd = GetActiveWindow()
lcClassName = GetClsName (hWnd)
hInstance = GetModuleHandle(0)
 
? "*** Input parameters"
? "Class name retrieved through the GetClassName:", lcClassName
? "Module handle:", hInstance
?
 
*| typedef struct _WNDCLASS {
*|     UINT       style;           0:4
*|     WNDPROC    lpfnWndProc;     4:4
*|     int        cbClsExtra;      8:4
*|     int        cbWndExtra;     12:4
*|     HINSTANCE  hInstance;      16:4
*|     HICON      hIcon;          20:4
*|     HCURSOR    hCursor;        24:4
*|     HBRUSH     hbrBackground;  28:4
*|     LPCTSTR    lpszMenuName;   32:4
*|     LPCTSTR    lpszClassName;  36:4
*| } WNDCLASS, *PWNDCLASS; total bytes: 40
#DEFINE WNDCLASS_SIZE  40
 
lcWndClass = Repli(Chr(0), WNDCLASS_SIZE)
= GetClassInfo (hInstance, lcClassName, @lcWndClass)
 
* While tested under VFP6+WinMe:
* Have fun: there is no guarantee for you to get the Class and Menu names back;
* despite of the GetClassInfo returns the proper pointers to 
* corresponding memory blocks -- lpszMenuName and lpszClassName
 
* quite often the VFP has its time and inspiration to fill these memory blocks
* with some other stuff within a jiffy before or after the GetClassInfo 
* finishes and returns control to the program; at least it looks like it does;
 
* switch between Try A and Try B -- you could find them returning different
* results, despite their identity; sometimes even Try A returns a garbage
 
* Try A:
= FillBuffer (@lcClassNameRet, buf2dword(SUBSTR(lcWndClass, 37,4)))
= FillBuffer (@lcMenuNameRet, buf2dword(SUBSTR(lcWndClass, 33,4)))
 
? "*** Output from the GetClassInfo"
? "Style:        ", buf2dword(SUBSTR(lcWndClass,  1,4))
? "lpfnWndProc:  ", buf2dword(SUBSTR(lcWndClass,  5,4))
? "cbClsExtra:   ", buf2dword(SUBSTR(lcWndClass,  9,4))
? "cbWndExtra:   ", buf2dword(SUBSTR(lcWndClass, 13,4))
? "hInstance:    ", buf2dword(SUBSTR(lcWndClass, 17,4))
? "hIcon:        ", buf2dword(SUBSTR(lcWndClass, 21,4))
? "hCursor:      ", buf2dword(SUBSTR(lcWndClass, 25,4))
? "hbrBackground:", buf2dword(SUBSTR(lcWndClass, 29,4))
? "lpszMenuName: ", buf2dword(SUBSTR(lcWndClass, 33,4))
? "lpszClassName:", buf2dword(SUBSTR(lcWndClass, 37,4))
?
 
* Try B:
*= FillBuffer (@lcClassNameRet, buf2dword(SUBSTR(lcWndClass, 37,4)))
*= FillBuffer (@lcMenuNameRet, buf2dword(SUBSTR(lcWndClass, 33,4)))
 
? "Class name:   ", lcClassNameRet
? "Menu name:    ", lcMenuNameRet
 
PROCEDURE  FillBuffer (lcBuffer, lnPtr)
    IF lnPtr = 0
        lcBuffer = ""
    ELSE
        = Heap2String (@lcBuffer, lnPtr, Len(lcBuffer))
        lcBuffer = SUBSTR(lcBuffer, 1, AT(Chr(0), lcBuffer)-1)
    ENDIF
 
FUNCTION  GetClsName (lnHwnd)
    LOCAL lnBufsize, lcClassName
    lnBufsize = 250
    lcClassName = SPACE(lnBufsize)
    lnBufsize = GetClassName (lnHwnd, @lcClassName, lnBufsize)
RETURN  SUBSTR(lcClassName, 1, lnBufsize)
 
FUNCTION  buf2dword (lcBuffer)
RETURN Asc(SUBSTR(lcBuffer, 1,1)) + ;
    Asc(SUBSTR(lcBuffer, 2,1)) * 256 +;
    Asc(SUBSTR(lcBuffer, 3,1)) * 65536 +;
    Asc(SUBSTR(lcBuffer, 4,1)) * 16777216
 
PROCEDURE  decl
    DECLARE INTEGER GetActiveWindow IN user32
    DECLARE INTEGER GetModuleHandle IN kernel32 STRING lpModuleName
 
    DECLARE RtlMoveMemory IN kernel32 As Heap2String;
        STRING @Dest, INTEGER Src, INTEGER nLength
 
    DECLARE INTEGER GetClassName IN user32;
        INTEGER hWnd, STRING lpClassName, INTEGER nMaxCount
 
    DECLARE INTEGER GetClassInfo IN user32;
        INTEGER hInstance, STRING lpClassName, STRING @lpWndClass
 
 

User rating: 0/10 (0 votes)
Rate this code sample:
  • ~
3632 bytes  
Created: 2001-12-02 15:15:22  
Modified: 2005-10-27 19:03:47  
Visits in 7 days: 64  
Listed functions:
GetActiveWindow
GetClassInfo
GetClassName
GetModuleHandle
Printer friendly API declarations
My comment:
While tested under VFP6+WinMe:

Have fun: there is no guarantee for you to get the Class and Menu names back, despite of the GetClassInfo returns the proper pointers to corresponding memory blocks -- lpszMenuName and lpszClassName.

Quite often the VFP has its time and inspiration to fill these memory blocks with some other stuff within a jiffy before or after the GetClassInfo finishes and returns control to the program; at least it looks like it does.

Switch between Try A and Try B -- you could find them returning different results, despite their identity; sometimes even Try A returns a garbage.

* * *
Having Microsoft Spy++ installed (included in all Visual Studio versions), you may want to spy on some VFP windows. For example, WAIT WINDOW window. Its window class is VFP664000002 for VFP6, vfp884000003 for VFP8 and vfp994000003 for VFP9. I have no data for other VFP versions.

When FoxPro starts, it creates two or three windows of this class, all owned by the main VFP window, and hides them. Every time WAIT WINDOW command is issued, one more WW window is created, the only one visible. Eventually this window is destroyed as a result of WAIT CLEAR or keypress etc.

Each WW window has separate device context, that means it is drawn separately. All of them share same WinProc. It is possible to use SetClassLong to change Window style for all eventually created WW windows.

An instance of FoxPro Timer Control, when started, ticks behind a WAIT WINDOW, which opens possibilty for minor adjustments and pranks.
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-2013 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.1.55-log), the Open Source standard SQL database, AceHTML Freeware Version 4, freeware HTML Editor of choice.   Hosted by Korax Online Inc.
Last Topics Visited (107.20.7.65)
4 sec.Function: 'SetKeyboardState'
19.38 min.Example: 'Obtaining names and positions for shortcuts located on the Windows Desktop'
19.43 min.Function: 'GetRgnBox'
Function group: 'Region'
19.48 min.Example: 'Creating a clipping region from the path selected into the device context of a form'
33.87 min.Example: 'How to check whether the system is 32-bit or 64-bit'
33.92 min.Example: 'How to retrieve version information for the specified file'
3.88 hrs.Example: 'How to create a service object'
 Example: 'How to display Windows On-Screen Keyboard'
3.91 hrs.Function: 'JetBeginSession'
Function group: 'Extensible Storage Engine (ESE, Jet Blue)'
3.99 hrs.Example: 'Finding out if the current user is the Guest account'
Google
Advertise here!