Using the Win32 Windows Approach
Once upon a time (about 15 years ago -- my how time flies when you're having fun!), most commercial Windows applications were written in C or C++ and used the "Win32" library to display and interact internally with Windows controls (buttons, textboxes, lists, radio buttons, etc.).
If you are documenting such an application, you will do well to go into
Project settings > Screen capturing
and at the bottom of the settings area, ensure the color is different for each different screen capture scenario. (I changed "Accesssible objects" from orange to bright green so I could see what approach Dr.Explain was using to analyze the window in queston.)
Changing the Accessible Objects Boundary Color to a Unique Color
While Dr.Explain does a GREAT job analyzing this window with the Accessible Objects approach:
Result of Using Dr.Explain's Accessible Objects Approach to Analyze The Spy++ Window Search Dialog Box
you can get Dr.Explain to analyze it using the Win32 approach if you want to by making your own "Capturing scenario" if you haven't already done so:
Project Settings > Screen capturing > Capture scenario > Edit (the pencil and paper button)
and UNCHECK the "Accessible objects" checkbox to force Dr.Explain to use the Win32 approach to analyze the capture areas of your application.
Unchecking Accessible Objects Option to Force Dr.Explain to Use Win32 Windows Analysis
Be sure to click OK, OK so that it saves your custom settings.
Note that Dr.Explain correctly does not allow me to edit the "Standard" Capture scenario rules, but it does allow me to make a copy of them. I accept, and give it my own name so that I know it is my temporary Capture Scenario rules so I can turn it off later when I don't want to use my customizations any more.
Name: Vics Custom 01 (English)
Description: Copy of <Standard> to experiment.
