3. WinID Readout Pane

WinID Readout Pane (Advanced mode)

Going from left to right starting from the top down here is the meaning of information displayed in the Readout Pane:
(To select which type of information is currently displayed in the Readout Pane use Display Options available from the Main Menu.)

• Pos: Current position of the mouse pointer in pixels relative to the top left corner of the screen, in format X, Y - where X grows from the left side of the screen towards the right side, and Y - from the top to bottom;
  
  Low Privilege! may be displayed on the right side next to Pos: field if WinID is running under user account with limited privileges. This will prevent WinID from retrieving certain types of information about controls accurately. These types are marked with an asterisk (*) below in the description.
   
  INFORMATION: We strongly recommend running WinID from the administrator's account or an account with administrative privileges on Windows NT family Operating System.
   
  Limited func! may be displayed on the right side next to Pos: field if many of WinID's functions are disabled due to limitations imposed by the Operating System. This may happen on older versions of Windows NT family Operating System or on Windows 95/98/Me. These types are marked with an asterisk (*) below in the description.
   
• HWND: Hexadecimal window handle of the Control [more info];
   
  INFORMATION: The Operating System uses window handles to represent its system resources allocated for each window/control. Each window handle is unique throughout the system. Window handles could be shared between different processes.
   
  ID: Hexadecimal ID of the Control. It could be an ID used to identify it in the dialog window, or an ID value given to it at creation time;
   
  INFORMATION: This ID value is not used system-wide and is the means for creators of window/control to ID it within an application. The meaning of this ID value is application specific.
   
  ENB: If highlighted, means that the Control is enabled [more info];
  VSB: If highlighted, means that the Control is visible [more info] (for limitation of this feature see Show Invisible option);
  UNC: If highlighted, means that the Control is a native Unicode Window [more info];
   
  INFORMATION: Control is enabled when it can receive the keyboard focus from the system.
   
  INFORMATION: Control is visible when its window is currently painted on the screen. Some controls/windows might not be destroyed and kept invisible by the Operating System or other applications. This method is implemented in the property pages dialog boxes.
   
  INFORMATION: Control is a native Unicode Window if its window class was created using RegisterClassExW function. Unicode controls are different from ANSI controls in a way they can work with extended character sets usually used for international and special characters.
   
• Title: This line contains title of the Control put into double-quotation marks. The meaning of a title depends on the Control itself. For a window with a system bar, the title is a window caption text. For some controls title is the contents of control itself (like edit box, static box, etc). Some controls may return an empty title [more info];
   
  INFORMATION: If title is too long to be displayed in the Readout Pane, it is abbreviated using ellipsis at the end. To retrieve the longer version of title text use Capture Shot feature.
   
  INFORMATION: The length of a title text that WinID can retrieve from the Control should not exceed 260 characters, including punctuation marks and spaces. If a title is longer than 260 characters, it is abbreviated and '>>>' symbols are put at the end.
   
  INFORMATION: WinID may display "<ERROR: Ctrl Hung>" or "<ERROR: Ctrl Not Responding>" as a title if the Control failed to respond within 400 milliseconds to the message sent by WinID. This does not always mean that the Control belongs to an application that is "hung". Try moving mouse over the Control for several seconds to make sure that this message repeats. In some cases windows and controls may become non-responding in the following situations:
  1. If process the Control belongs to is currently loading up. This is the time when program takes up most of CPU and Operating System resources, thus on a slower system the Control may temporarily stop processing messages in the message queue. In this case WinID may also stop updating its Readout Pane temporarily if it's running in the same Base Priority as the Control. To make WinID update the Readout Pane in this situation you have to increase its priority level to above Normal in the Settings window;
  2. If the Control is performing a long task. Although this is against Windows guidelines to keep control busy so that it does not process messages, some windows/controls may neglect this stipulation. In this situation the Control may remain as not responding for the time longer than 400 milliseconds, and sometimes even up to several seconds;
  3. If window (and process the Control belongs to) is "hung". This may happen by many reasons. One of them is when a program encounters an error and enters a dead loop. In this case the Control may remain non-responding for a long time and sometimes even indefinitely. WARNING: It is recommended that you don't use WinID in Highlight Selected Control Mode on "hung" controls/windows.
      
• Class: This line has a class name of window class of the Control put into double-quotation marks. Since each control should have a class name this string could not be empty. You can distinguish between types of controls by looking at their class names [more info];
   
  INFORMATION: If window class is a system class WinID puts and asterisk (*) after it's class name. The system class is a class that was registered by the Operating System.
   
  <RECOGNIZED_CLASS> is a C++ #define preprocessor variable name or a descriptive string for the Control's class name if it's recognized by WinID. This name is displayed in red letters if it's a C++ #define variable (e.g. WC_STATIC), or in purple inside single-quotation marks (e.g. 'Dialog Box') if it's a recognized class that doesn't have a C++ #define variable [more info].
   
  INFORMATION: The class name is the way Operating System can distinguish between different windows/controls during operation. The window class for control is the basic implementation of its message processing routines and control functions, which makes control to exist in the system.
   
  INFORMATION: The class name and it's C++ counterpart is detected and displayed automatically by WinID in despite of the Manual Class Recognition Mode selection.
  INFORMATION: WinID will display control styles for recognized classes and have special features enabled in Captured Shots window.
   
• HMODULE: Hexadecimal module handle of the Control [more info];
   
  INFORMATION: The module is an executable file loaded in the context of a program that a class implementation of control is residing in. It can be also called a container for the control code located in the file system. Module handles are unique throughout the system.
   
  Atom: Hexadecimal atom value of the Control's window class [more info];
   
  INFORMATION: Atom handle is an alternative way to identify control class. Unlike class name, atom handle is unique throughout the system.

• WndProc: Hexadecimal handle of Window Procedure of the Control [more info];
   
  INFORMATION: Window Procedure is a window class routine that handles all Windows messages sent to the Control. Each control/window should have a Window Procedure of its own or the one registered by the system or by another module.
   
  INFORMATION: WinID will display double-asterisk (**) next to the WndProc field if the Control is subclassed. Subclassing is an option to attach user-defined message handler (i.e. Window Procedure) to an already existing one. It is often used to add functionality to existing classes. [more info]
   
  INFORMATION: Handle obtained through this field is valid only in the context of a process it belongs to.
   
  Menu RSRC: Hexadecimal resource ID or string name for default menu of the Control. If it's a string name it is put into double-quotation marks [more info];
   
• HDC (Wnd): Hexadecimal handle to window device context of the Control [more info];
   
  INFORMATION: In case control that this device context stands for has a window region one of the following might be displayed next to HDC (Wnd) field:
  • [cpx] - if control has a complex region [more info];
  • [smp] - if control has a simple region [more info];
  • [nul] - if control has a null region [more info];
  • If nothing is displayed it means that control has no window region associated with it and its window is a simple rectangle.
  
   HDC (Client): Hexadecimal handle to device context of the Control's client area [more info];
   
  INFORMATION: Window device context and client area device context could be represented by the same handle if control does not have system (title) bar or a border frame around it.
   
  INFORMATION: Device contexts are attributed to their window handles and are not unique throughout the system.
   
• HICON: Hexadecimal handle to an icon associated with the Control [more info];
   
  HICON(sm): Hexadecimal handle to a small icon displayed in a title (system) bar of the Control [more info];
   
• HCURSOR: Hexadecimal handle to a mouse cursor associated with the Control given to it during class registration [more info];
   
  Brush: C++ #define preprocessor value for the background color of the Control. Hexadecimal color index is included in parenthesis [more info];
  HBRUSH: Hexadecimal handle to a brush used to paint background of the Control [more info];

• Class Styles: Hexadecimal value of the Control's class styles that is composed of individual style flags by Boolean OR operation. All flags are presented on the next lines in the text form as C++ #define variables [more info];
   
  Xtra (Cls, Wnd): Two hexadecimal values of the size in bytes of an extra memory associated with window class and window of the Control, accordingly [more info];
   
• <CLASS_STYLES> is enumeration of all class styles currently recognized by WinID presented as C++ #define preprocessor variables. Highlighted values are the ones that are actually enabled for the Control and are included in the Class Styles hexadecimal value [more info];

• Proc ID: Hexadecimal ID of the Process. Each process could be identified by its ID, thus Proc ID is unique throughout the system [more info];
   
  <[^N]>: Might be displayed on the right side of the Proc ID field if WinID was not able to open the Process with the full access to it. Basically it means that WinID had to adjust access rights value to open the Process. N stands for Process Open Level and signifies which access rights flags were used [more info]. You can get them from this table:
  • 0 = ACCESS_SYSTEM_SECURITY | PROCESS_ALL_ACCESS;
  • 1 = ACCESS_SYSTEM_SECURITY | PROCESS_QUERY_INFORMATION | READ_CONTROL | PROCESS_VM_READ | PROCESS_VM_OPERATION;
  • 2 = PROCESS_QUERY_INFORMATION | READ_CONTROL | PROCESS_VM_READ | PROCESS_VM_OPERATION;
  • 3 = ACCESS_SYSTEM_SECURITY | PROCESS_QUERY_INFORMATION | READ_CONTROL | PROCESS_VM_READ;
  • 4 = PROCESS_QUERY_INFORMATION | READ_CONTROL | PROCESS_VM_READ;
  • 5 = PROCESS_QUERY_INFORMATION | READ_CONTROL.
     
    INFORMATION: The value of 0 is not displayed in the Readout Pane. This level signifies the full access to the Process.
     
    INFORMATION: If Process Open Level is not zero this means that some process-related data might not be retrieved by WinID. The greater this level is, the more chance that WinID will fail to retrieve certain information. To see what information might be affected by this check MSDN descriptions in the "more info" links for a field of interest regarding access rights flags corresponding to Process Open Level value.
     
  Ver: Version of the Process [more info];
   
  *[Wow64]: Might be displayed on the right side of the Ver: field if the Process is running under Windows on Windows64 emulator [more info];
  *[Debugged]: Might be displayed on the right side of the Ver: field if the Process is being debugged be a user-mode debugger [more info];
   
  INFORMATION: A process is considered as being debugged if it is running in the context of a debugging program.
   
• <PRIORITY_CLASS> is priority class for the Process. It might be a C++ #define preprocessor value if priority class numeric value is recognized by WinID, otherwise the value itself is displayed as a hexadecimal number. The graph representing priority class is displayed on the right-hand side. The length and color of the bar inside the graph represents priority level - bigger bar and color closer to red signifies higher priority level [more info];
   
  *[Boost]: Might be displayed on the right side of priority class graph if priority boost is enabled for the Process [more info];
   
  INFORMATION: When a process that uses NORMAL_PRIORITY_CLASS is brought to the foreground, the scheduler boosts the priority class of the process associated with the foreground window, so that it is greater than or equal to the priority class of any background processes. The priority class returns to its original setting when the process is no longer in the foreground.
   
• *Crtd: Local time the Process was created. Format: MM/DD HH:MN:SS, where MM=Month, DD=Day, HH=Hour (military), MN=Minutes, SS=Seconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.
   
  *Krnl: Time interval the Process was executed in the KERNEL system module since its creation. Format: MM:SS.MS, where MM=Minutes, SS=Seconds, MS=Milliseconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.
   
  *Usr: Time interval the Process was executed in the USER system module since its creation. Format: MM:SS.MS, where MM=Minutes, SS=Seconds, MS=Milliseconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.
   
• Affinity Msk: Hexadecimal value for the affinity mask of the process [more info], or
  *HANDLEs: If supported by the system, this value is displayed instead of Affinity Msk. It has a total number of open handles currently used by the Process [more info];
   
  INFORMATION: The affinity mask is a bit vector in which each bit represents the processors that the Process is allowed to run on. If affinity mask value if not displayed in the Readout Pane it can still be accessed through Captured Shots dialog window.
   
  INFORMATION: Handles are used throughout the Operating System. They represent internal IDs of resources that system allocated for the Process. In this regard, the bigger the number of handles is, the more resources the Process is using.
   
  INFORMATION: HANDLEs value is supported starting from Windows XP SP1 and later.
   
  *GDI: Number of open handles from the GDI (Graphics Device Interface) system module currently used by the Process [more info];
   
  INFORMATION: Handles from the GDI module represent part of the Process that deals with GUI (Graphics User Interface), graphics and drawing in general.
   
  *USER: Number of open handles from the USER system module currently used by the Process [more info];
   
  INFORMATION: Handles from the USER module represent internal part of the Process that deals with creation and operation of windows, messaging and communication between windows, controls, threads, processes, etc. In other words, everything else besides GUI and basic memory management that is implemented in the KERNEL module.

• *Alloc Base: Hexadecimal value of the load address of the Module [more info];
   
  INFORMATION: The address returned is the base address.
   
  *Entr: Hexadecimal value of the entry point address of the Module [more info];
   
  INFORMATION: The address returned is the base address. The module entry point is the location called during process startup, thread startup, process shutdown, and thread shutdown. It is not necessarily the address of the DllMain or WinMain function. This information is retrieved from the Portable Executable (PE) header.
   
  *Sz: Hexadecimal value of the size of the linear space that the Module occupies in bytes [more info];
   
  INFORMATION: This information is retrieved from the Portable Executable (PE) header.
   
• *WrkSet Sz: Hexadecimal value of the current working set size of the Process in bytes [more info];
   
  INFORMATION: The "working set" of the Process is the set of memory pages currently visible to the Process in physical RAM memory. These pages are resident and available for an application to use without triggering a page fault.
   
  *Min: Hexadecimal value of the minimum working set size of the Process in bytes [more info];
   
  INFORMATION: The minimum working set size affects the virtual memory paging behavior of the Process. The virtual memory manager attempts to keep at least this much memory resident in the Process whenever the process is active.
   
  *Max: Hexadecimal value of the maximum working set size of the Process in bytes [more info];
   
  INFORMATION: The maximum working set size affects the virtual memory paging behavior of the Process. The virtual memory manager attempts to keep no more than this much memory resident in the Process whenever the Process is active when memory is in short supply.
   
• *PKs WrkSet: Hexadecimal value of the peak working set size of the Process in bytes [more info];
   
  INFORMATION: The working set is the amount of memory physically mapped to the Process context at a given time.
   
  *PgF: Hexadecimal value of the peak space allocated in the page file for the Process in bytes [more info];
   
  INFORMATION: The page file usage represents how much memory is set aside for the Process in the system paging file. When memory usage is too high, the virtual memory manager pages selected memory to disk. When a thread needs a page that is not in memory, the memory manager reloads it from the paging file.
   
  *QPP: Hexadecimal value of the peak of paged pool usage of the Process in bytes [more info];
   
  INFORMATION: Memory in the paged pool is system memory that can be transferred to the paging file on disk (paged) when it is not being used.
   
• *Usage QnPP: Hexadecimal value of the current nonpaged pool usage of the Process in bytes [more info];
   
  INFORMATION: Memory in the nonpaged pool is system memory that cannot be paged to disk as long as the corresponding objects are allocated.
   
  *PgF: Hexadecimal value of the current space allocated in the page file for the Process in bytes. Those pages may or may not be in memory [more info];
   
  INFORMATION: The page file usage represents how much memory is set aside for the Process in the system paging file. When memory usage is too high, the virtual memory manager pages selected memory to disk. When a thread needs a page that is not in memory, the memory manager reloads it from the paging file.
   
  *QPP: Hexadecimal value of the current paged pool usage of the Process in bytes [more info];
   
  INFORMATION: Memory in the paged pool is system memory that can be transferred to the paging file on disk (paged) when it is not being used.
   
• *I/O Info RD: Decimal value of the number of I/O read operations performed by the Process [more info];
   
  INFORMATION: Input/Output operation (or I/O) is any transaction between CPU + RAM and any other computer devices including but not limited to keyboard, mouse, video and sound cards, etc.
   
  *WR: Decimal value of the number of I/O write operations performed by the Process [more info];
   
  *OT: Decimal value of the number of I/O operations performed by the Process, other than read and write operations [more info];
   
• *I/O Trnsf RT: Hexadecimal value of the number of bytes read by the Process through I/O operations [more info];
   
  INFORMATION: Input/Output operation (or I/O) is any transaction between CPU + RAM and any other computer devices including but not limited to keyboard, mouse, video and sound cards, etc.
   
  *WT: Hexadecimal value of the number of bytes written by the Process through I/O operations [more info];
   
  *OT: Hexadecimal value of the number of bytes transferred during operations other than read and write I/O operations by the Process [more info];

• *<PROCESS_PRIVILEGES> is enumeration of all process privileges currently recognized by WinID presented as C++ #define preprocessor values. Highlighted values are the ones currently being on for the Process [more info]. There are two types of highlighting:
  1. Dark Green Color - if a privilege is enabled for the Process;
  2. Light Green Color - if a privilege is enabled by default for the Process.
   
  INFORMATION: If WinID is not capable of retrieving privilege values for the Process it displays all of them using a pale pink color. Process privileges are not supported by Windows 95/98/ME Operating Systems.
   
  INFORMATION: These privileges could not be combined using Boolean OR operation.

• Thread ID: Hexadecimal ID of the Thread. Each thread could be identified by its ID, thus Thread ID is unique throughout the system [more info];
   
• <THREAD_PRIORITY> is priority value for the Thread [more info]. It might be a C++ #define preprocessor value if priority numeric value is recognized by WinID, otherwise the value itself is displayed as a hexadecimal number. The graph representing the Thread priority value is displayed on the right-hand side. The length and color of the bar inside the graph represents priority level - bigger bar and color closer to red signifies higher priority level.
   
  *[Boost]: Might be displayed on the right side of the Thread priority level graph if priority boost is enabled for the Thread [more info];
   
• *Crtd: Local time the Thread was created. Format: MM/DD HH:MN:SS, where MM=Month, DD=Day, HH=Hour (military), MN=Minutes, SS=Seconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.
   
  *Krnl: Time interval the Thread was executed in the KERNEL system module since its creation. Format: MM:SS.MS, where MM=Minutes, SS=Seconds, MS=Milliseconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.
   
  *Usr: Time interval the Thread was executed in the USER system module since its creation. Format: MM:SS.MS, where MM=Minutes, SS=Seconds, MS=Milliseconds [more info];
   
  INFORMATION: The accuracy of this value depends on the Operating System.

• Base Priority: B(F) displays two values of the base priority of the Thread, where 'B' stands for a decimal value of base priority when the Thread is not on the foreground, and 'F' - for base priority decimal value when the Thread is on the foreground. Two graphs representing base priority are displayed on the right-hand side. The top graph stands for base priority when the Thread is not on the foreground, the bottom graph - when the Thread is on the foreground. The length and color of bars inside the graph represents priority level - bigger bar and color closer to red signifies higher priority level [more info].
   
  INFORMATION: The priority level of the Thread is determined by both the priority class of the Process and priority level of the Thread. The priority class and priority level are combined to form the base priority of each thread.
   
  INFORMATION: The Thread is said to be on the foreground if control or window that belongs to it has a keyboard focus. In case of a window with a system bar being on the foreground its title bar is highlighted.
   
• Img: [<TYPE>] <PATH> contains a full path to the image file for the Process and a type of the executable file it refers to [more info]. The following types are supported by WinID:
  • NoX - The file is not an executable;
  • 32bit-GUI - The file is 32-bit GUI executable;
  • 32bit-Cnsl - The file is 32-bit Console executable;
  • 32bit-Ntv - The file is 32-bit Native driver;
  • 32bit-OS/2 Cnsl - The file is 32-bit OS/2 Console executable;
  • 32bit-Psx Cnsl - The file is 32-bit POSIX Console executable;
  • 32bit-Ntv9x - The file is 32-bit Native Windows9x driver;
  • 32bit-CE GUI - The file is 32-bit Windows CE GUI executable;
  • 32bit-xbx - The file is 32-bit Xbox executable;
  • 16bit - The file is 16-bit executable;
  • DOS - The file is DOS executable;
  • VxD - The file is a VxD device driver;
  • Oth - The type of file is not supported by WinID;
  • Err - Could not open specified path to determine type.
  
  INFORMATION: The image file is an executable file that the Process originated from. It can also be called a container located in the file system that the Process code is residing in. Each process has an image file associated with it. Windows Operating System allows users to start processes by running their image files usually by double-clicking its icons in the Windows Explorer or through the Run option in the Start menu.
   
  INFORMATION: The path to the image file might be abbreviated in the Readout Pane due to limited width of the screen. In this case the ellipsis is used in the middle of the path. To retrieve the full path use Capture Shot option.
   
• Mod: [<TYPE>] <PATH> contains a full path to the module file in which the code for control underneath the mouse pointer is residing in and a type of executable file it refers to [more info]. For the types of executables supported by WinID check description of the image file path for the Process above;
   
  INFORMATION: The module file is an executable file that a class implementation of control is residing in. It can be also called a container for the control code located in the file system. In some cases module file path might coincide with image file path for the Process. WinID might not be able to retrieve module paths for some controls.
   
  INFORMATION: The path to the module file might be abbreviated in the Readout Pane due to limited width of the screen. In this case the ellipsis is used in the middle of the path. To retrieve the full path use Capture Shot option.

• HINST: Hexadecimal instance handle for the Process [more info];
   
  INFORMATION: When a process starts up it receives its instance handle through the WinMain function. Instance handles for processes are not unique throughout the system and might be used only within a single process.
   
  *ShutDn Ord (N): Displays priority level at which the Process might be closed during the system shut-down, where 'N' is a hexadecimal value of this priority level, or 0xErr if this value could not be retrieved from the Process. The graph representing shut-down priority level is displayed on the right-hand side. The length of the bar inside the graph represents priority level - bigger bar signifies higher priority level [more info];
   
  INFORMATION: When system shut-down is initiated the Operating System uses shut-down privileges of all running processes to determine which ones of them should be first to receive closing notifications - processes with the higher shut-down priority level close first. This feature is not supported by Windows 95/98/ME Operating Systems.
   
  *NORTY might be displayed on the right-hand side of the shut-down priority graph if the Process does not require user confirmation to terminate after the system shut-down if it did not close within specified timeout period [more info];
   
  INFORMATION: When this value is set for the Process and if the Process takes longer than the specified timeout to shut down, the system does not display a retry dialog box for the user. Instead, it causes the Process to terminate unconditionally.
   
• Parent: hWnd=H, Class="C" - 'H' is hexadecimal handle to a parent window of control underneath the mouse pointer, and 'C' is a window class name for parent window put into double-quotation marks [more info], or
  No parent window if control underneath the mouse pointer has no parent window;

• Style: Hexadecimal value of window styles of the Control that is composed of individual style flags by Boolean OR operation. These flags are presented below in a text form as C++ #define variables in <WINDOW_STYLES> and <CONTROL_STYLES> sections if WinID recognized window class for the Control [more info];
   
  ExStyle: Hexadecimal value of extended window styles of the Control that is composed of individual style flags by Boolean OR operation. These flags are displayed below in a text form as C++ #define variables in <EXTENDED_WINDOWS_STYLES> section [more info];
   
• <WINDOW_STYLES> (left side) is enumeration of all enabled window styles for the Control that are included in the Style hexadecimal value. These window style values are presented as C++ #define variables and are displayed vertically. The number of enabled window styles depends on the Control itself;
   
• <EXTENDED_WINDOW_STYLES> (left side) is enumeration of all enabled extended window styles for the Control that are included in the ExStyle hexadecimal value. These extended window style values are presented as C++ #define variables and are displayed vertically right below the <WINDOW_STYLES> section. The number of enabled extended window styles depends on the Control itself;
   
• <CONTROL_STYLES> (right side) is enumeration of all enabled control styles for the Control that are included in the Style hexadecimal value. These control style values are presented as C++ #define variables and are displayed vertically. The type of control styles and their number depends on the Control itself and the window class currently used to identify the Control. If WinID is running in the Manual Class Recognition Mode these control styles are attributed to the window class selected manually. In this case WinID uses green color to display control styles if control class is not matching the one selected in Manual Class Recognition Mode, or purple color if it does. If Manual Class Recognition Mode is off WinID attempts to determine the Control class automatically and display appropriate control styles for the Control. Only if window class for the Control was detected, or if it is selected manually, WinID displays C++ #define variables for control styles [more info];
   
  INFORMATION: If any of the flags in the Style value are not recognized by WinID they are displayed at the bottom of the <CONTROL_STYLES> as a hexadecimal value.
   
  INFORMATION: It is recommended that you let WinID determine window classes and styles automatically.
   
• <EXTENDED_CONTROL_STYLES> (right side) is enumeration of all enabled extended control styles for the Control. These extended control style values are presented as C++ #define variables and are displayed vertically right below the <CONTROL_STYLES> section. The number of extended control styles depends on the Control itself;
   
  INFORMATION: Extended control styles for the Control are not included in the Style or ExStyle hexadecimal values.
   
• <EXTRA_CONTROL_INFO> (right side) is enumeration of extra information for the Control if it is available. This information is presented as C++ #define variables and is displayed at the bottom below <CONTROL_STYLES> and <EXTENDED_CONTROL_STYLES> in dark blue color.
   
  INFORMATION: An example of extra control information could be event mask flags for a RichEdit control.
   
  INFORMATION: The space required to display all window and control styles for the Control could vary depending on how much information WinID was able to retrieve from the Control. In case some of the information is displayed below the bottom of the Readout Pane and becomes invisible, WinID will draw red arrow pointers at the bottom of the Readout to signify that information was not displayed in the Readout Pane entirely. To have more space in the Readout for window and control styles uncheck types of information that you don't need in Display Options menu, or resize WinID's window using mouse pointer.