From d6ad3e6a17f7bcae90a31a94dd2b99222facd068 Mon Sep 17 00:00:00 2001 From: "trop[bot]" Date: Tue, 28 May 2019 14:21:17 -0700 Subject: [PATCH] docs: clarify that 'second-instance' is only emitted when the second instance calls `app.requestSingleInstanceLock()` (#18384) --- docs/api/app.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/api/app.md b/docs/api/app.md index ca8b89b912067..3173f27ffabb4 100644 --- a/docs/api/app.md +++ b/docs/api/app.md @@ -390,8 +390,10 @@ Returns: * `workingDirectory` String - The second instance's working directory This event will be emitted inside the primary instance of your application -when a second instance has been executed. `argv` is an Array of the second instance's -command line arguments, and `workingDirectory` is its current working directory. Usually +when a second instance has been executed and calls `app.requestSingleInstanceLock()`. + +`argv` is an Array of the second instance's command line arguments, +and `workingDirectory` is its current working directory. Usually applications respond to this by making their primary window focused and non-minimized.