This occurs because app module cleanup happens whenever a focus event is
fired. When you close the app, focus hits another app (Notepad in your
example), but the app you just closed is still in the process of
terminating, so the app module doesn't die yet. When the next focus event
happens, the old app has fully terminated, so its app module gets cleaned
up. Saying it is "intentional" might be too much, but it's not a bug as
such.
On Tue, Jan 10, 2017 at 12:52 AM, James Scholes <james@xxxxxxxxxxxxx> wrote:
Hi,
Once I close an application, the terminate method for that application's
app module only seems to be called after I've moved the focus myself.
E.g. I close the application window and focus returns to the window
behind the application, in this case Notepad, but the terminate method
for the closed application's app module is not called until I go to the
menu bar, desktop etc. Is this intended behaviour?
--
James Scholes
http://twitter.com/JamesScholes
----------------------------------------------------------------
NVDA add-ons: A list to discuss add-on code enhancements and for reporting
bugs.
Community addons are available from: http://addons.nvda-project.org
To send a message to the list: nvda-addons@xxxxxxxxxxxxx
To change your list settings/unsubscribe: //www.freelists.org/list/
nvda-addons
To contact list moderators: nvda-addons-moderators@xxxxxxxxxxxxx
