Including all the cases where the string "MOSFET" was not placed on the right place of the right window to be the correct trigger even for the required action.
So my system can ALWAYS work, whereas yours only works some of the time. SeeScreen is inherently compatible with every system, platform and application.
The next best alternative is a hodge podge conglomeration of many different complex technologies limited to simulating user actions on far fewer applications and operating system platforms.
I already posted one of several ways that my system can determine with certainty the exact set of FontInstances.