AutoHotkey Community

WinID is controls & windows identification utility that is both powerful and compact. It gives an easy way to retrieve information about MS Windows controls visually right off the screen.

WinID resembles Spy++ from the MS Visual Studio toolset but it also incorporates lots of its own handy features. It will be good for debugging C/C++/MFC/.NET and Visual Basic applications by a person who knows (or plans to learn) the MS Windows OS - programmer, debugger/tester, beginner, as well as learning more about how your favorite programs are made.

WinID is free to use for individual and noncommercial application

Here are some key features of "WinID":

· To use WinID all you have to do is to point mouse to control on the screen to get instant information about it;
· WinID is completely "transparent" for other programs and the OS;
· WinID retrieves a wealth of Windows NT compatible information, including: Control handle & title (text), control ID, control status (enabled, visible, Unicode), module handle, Window Procedure, menu, atom, icon, cursor and brush handles, window class styles, process ID, process priority, process creation and times, process memory and handle count stats, process privileges, main thread ID, priority and creation times, base priority, image file path, module file path, app instance handle, shut-down parameters & flags, parent window handle & class, window & control styles, extended styles, additional control-specific info, and much more;
· Using Capture Shot technique WinID can remember control state to be analyzed later;
· WinID can also retrieve command line, environment strings, image file path for a program by simply pointing to it through Capture Shot feature;
· Using Capture Shot you can copy and save retrieved information as text;
· WinID can highlight control it works with;
· WinID does Automatically Recognize many control classes;
· WinID can run with priority level above normal to have an upper hand over other apps;
· Use WinID to test other programs regarding resource and memory leaks

[More...]
[Screenshots]
[Manual]

Interestingly, the control class is different from the one shown in WindowSpy (SysTabControl32 vs. SysTabControl321)

It has a facility to copy the data to the clipboard

Windows Spy doesn't work properly on my decaying Win98.