Reported by jteh on 2010-04-12 03:39
Windows text consoels use EVENT_CONSOLE_* winEvents. These events are always delivered out-of-context, even if you set a winEvent hook for in-context events. Currently, nvdaHelper hooks all winEvents, including these. These events cause some minor performance degradation, which is quite noticeable when, for example, displaying several thousand lines of text to a console. This is made worse because nvdaHelper 32, nvdaHelper 64 and NVDA itself are all listening for these events. There's absolutely no reason for nvdaHelper to listen to them, so we should stop doing so.
Reported by jteh on 2010-04-12 03:39
Windows text consoels use EVENT_CONSOLE_* winEvents. These events are always delivered out-of-context, even if you set a winEvent hook for in-context events. Currently, nvdaHelper hooks all winEvents, including these. These events cause some minor performance degradation, which is quite noticeable when, for example, displaying several thousand lines of text to a console. This is made worse because nvdaHelper 32, nvdaHelper 64 and NVDA itself are all listening for these events. There's absolutely no reason for nvdaHelper to listen to them, so we should stop doing so.