Electron event emitter error while app.quit with closing all open renderer processes
up vote
0
down vote
favorite
I have one main window listing all available servers with a status button which has the id of the server. An info window is opened after pressing the related status button - passing the id to the copy of info window, making the status button disabled. If the info window is closed, the info window passes back the id to the main window so it makes the status button enabled again. To do that, I'm using main.js
as a proxy, listening to the renderer processes and exchange information between main window and info window.
The thing that I'm trying to do is to list servers. If they are online, get some information from multiple servers at once on different renderer processes (instance of info window).
The problem is I want all info windows to be closed if the main window is closed.
// App ready
app.on('ready', ()=>{
mainWindow = new BrowserWindow({x : 0, y : 0 , width : 500, height: 600});
mainWindow.loadURL(url.format({
pathname : path.join(__dirname, 'windows', 'mainWindow.html'),
protocol : 'file',
slashes : true
}));
// Close the app if main window closed
mainWindow.on('close', (e) => {
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind => {
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
});
});
While creating info window, I add a custom field to the BrowserWindow
object:
BrowserWindow {
_events:
{ blur: [Function],
focus: [Function],
show: [Function: visibilityChanged],
hide: [Function: visibilityChanged],
minimize: [Function: visibilityChanged],
maximize: [Function: visibilityChanged],
restore: [Function: visibilityChanged],
close: [Function: callIntoRenderer] },
_eventsCount: 8,
devToolsWebContents: [Getter],
custom: { server_id: '3' } }
So with the help of the custom field, I can get all opened server info instances.
But when I click close, the following part is failing at main.js
;
ipcMain.on('window_closed', (e, item)=>{
mainWindow.webContents.send('button_enable', item);
});
It raises the following error.
main.js:53
is the line ipcMain.on('window_closed'...
. By the way, if I omit this line everything works perfectly.
node.js electron
add a comment |
up vote
0
down vote
favorite
I have one main window listing all available servers with a status button which has the id of the server. An info window is opened after pressing the related status button - passing the id to the copy of info window, making the status button disabled. If the info window is closed, the info window passes back the id to the main window so it makes the status button enabled again. To do that, I'm using main.js
as a proxy, listening to the renderer processes and exchange information between main window and info window.
The thing that I'm trying to do is to list servers. If they are online, get some information from multiple servers at once on different renderer processes (instance of info window).
The problem is I want all info windows to be closed if the main window is closed.
// App ready
app.on('ready', ()=>{
mainWindow = new BrowserWindow({x : 0, y : 0 , width : 500, height: 600});
mainWindow.loadURL(url.format({
pathname : path.join(__dirname, 'windows', 'mainWindow.html'),
protocol : 'file',
slashes : true
}));
// Close the app if main window closed
mainWindow.on('close', (e) => {
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind => {
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
});
});
While creating info window, I add a custom field to the BrowserWindow
object:
BrowserWindow {
_events:
{ blur: [Function],
focus: [Function],
show: [Function: visibilityChanged],
hide: [Function: visibilityChanged],
minimize: [Function: visibilityChanged],
maximize: [Function: visibilityChanged],
restore: [Function: visibilityChanged],
close: [Function: callIntoRenderer] },
_eventsCount: 8,
devToolsWebContents: [Getter],
custom: { server_id: '3' } }
So with the help of the custom field, I can get all opened server info instances.
But when I click close, the following part is failing at main.js
;
ipcMain.on('window_closed', (e, item)=>{
mainWindow.webContents.send('button_enable', item);
});
It raises the following error.
main.js:53
is the line ipcMain.on('window_closed'...
. By the way, if I omit this line everything works perfectly.
node.js electron
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have one main window listing all available servers with a status button which has the id of the server. An info window is opened after pressing the related status button - passing the id to the copy of info window, making the status button disabled. If the info window is closed, the info window passes back the id to the main window so it makes the status button enabled again. To do that, I'm using main.js
as a proxy, listening to the renderer processes and exchange information between main window and info window.
The thing that I'm trying to do is to list servers. If they are online, get some information from multiple servers at once on different renderer processes (instance of info window).
The problem is I want all info windows to be closed if the main window is closed.
// App ready
app.on('ready', ()=>{
mainWindow = new BrowserWindow({x : 0, y : 0 , width : 500, height: 600});
mainWindow.loadURL(url.format({
pathname : path.join(__dirname, 'windows', 'mainWindow.html'),
protocol : 'file',
slashes : true
}));
// Close the app if main window closed
mainWindow.on('close', (e) => {
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind => {
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
});
});
While creating info window, I add a custom field to the BrowserWindow
object:
BrowserWindow {
_events:
{ blur: [Function],
focus: [Function],
show: [Function: visibilityChanged],
hide: [Function: visibilityChanged],
minimize: [Function: visibilityChanged],
maximize: [Function: visibilityChanged],
restore: [Function: visibilityChanged],
close: [Function: callIntoRenderer] },
_eventsCount: 8,
devToolsWebContents: [Getter],
custom: { server_id: '3' } }
So with the help of the custom field, I can get all opened server info instances.
But when I click close, the following part is failing at main.js
;
ipcMain.on('window_closed', (e, item)=>{
mainWindow.webContents.send('button_enable', item);
});
It raises the following error.
main.js:53
is the line ipcMain.on('window_closed'...
. By the way, if I omit this line everything works perfectly.
node.js electron
I have one main window listing all available servers with a status button which has the id of the server. An info window is opened after pressing the related status button - passing the id to the copy of info window, making the status button disabled. If the info window is closed, the info window passes back the id to the main window so it makes the status button enabled again. To do that, I'm using main.js
as a proxy, listening to the renderer processes and exchange information between main window and info window.
The thing that I'm trying to do is to list servers. If they are online, get some information from multiple servers at once on different renderer processes (instance of info window).
The problem is I want all info windows to be closed if the main window is closed.
// App ready
app.on('ready', ()=>{
mainWindow = new BrowserWindow({x : 0, y : 0 , width : 500, height: 600});
mainWindow.loadURL(url.format({
pathname : path.join(__dirname, 'windows', 'mainWindow.html'),
protocol : 'file',
slashes : true
}));
// Close the app if main window closed
mainWindow.on('close', (e) => {
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind => {
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
});
});
While creating info window, I add a custom field to the BrowserWindow
object:
BrowserWindow {
_events:
{ blur: [Function],
focus: [Function],
show: [Function: visibilityChanged],
hide: [Function: visibilityChanged],
minimize: [Function: visibilityChanged],
maximize: [Function: visibilityChanged],
restore: [Function: visibilityChanged],
close: [Function: callIntoRenderer] },
_eventsCount: 8,
devToolsWebContents: [Getter],
custom: { server_id: '3' } }
So with the help of the custom field, I can get all opened server info instances.
But when I click close, the following part is failing at main.js
;
ipcMain.on('window_closed', (e, item)=>{
mainWindow.webContents.send('button_enable', item);
});
It raises the following error.
main.js:53
is the line ipcMain.on('window_closed'...
. By the way, if I omit this line everything works perfectly.
node.js electron
node.js electron
edited Nov 19 at 22:23
pushkin
3,859102551
3,859102551
asked Nov 18 at 11:09
Kerem Cavusoglu
336
336
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
up vote
1
down vote
accepted
It looks like what's happening is your mainWindow
close
handler gets triggered which tells other windows to close, which then fires off the window_closed
event (I guess that's a custom event that you added?), and by the timemainWindow.webContents.send
is called, the mainWindow
's close handler finished and the window closed.
Simply add an isDestroyed
check before sending the message like so:
ipcMain.on('window_closed', (e, item)=>{
if (mainWindow && !mainWindow.isDestroyed())
mainWindow.webContents.send('button_enable', item);
});
Your other options (though arguably less optimal) are:
- Set a flag when the main window is closing and have the
window_closed
handler return out if it sees the flag (surely there's no reason to send abutton_enable
message if we're about to shut everything down):
let mainWindowIsClosing = false;
mainWindow.on('close', (e)=>{
mainWindowIsClosing = true;
...
wind.close();
...
});
ipcMain.on('window_closed', (e, item)=>{
if (mainWindowIsClosing) return;
mainWindow.webContents.send('button_enable', item);
});
- You can call the
destroy
method instead ofclose
to avoid firing theclose
event for child windows. (thoughwindow_closed
isn't an Electron event I believe, so it depends on how you've hooked everything up):
mainWindow.on('close', (e)=>{
...
wind.destroy();
});
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
add a comment |
up vote
0
down vote
Found a solution as follows;
mainWindow.on('close', (e)=>{
mainWindow = null;
try{
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind=>{
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
}catch(e){
console.log(e);
}
});
Before closing the main window, i set the mainwindow to null. When an info window is closed, check if its not set to null, send the mainwindow an info window is closed and its status button should be enabled;
ipcMain.on('window_closed', (e, item)=>{
try {
if(mainWindow !== null){
mainWindow.webContents.send('button_enable', item);
}
} catch (error) {
console.log(error);
}
});
I wonder, if you add aclosed
handler on themainWindow
, does it get triggered after younull
it out? Typically, you should null out the window in theclosed
handler, notclose
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate
– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
add a comment |
up vote
0
down vote
You should use Child/Parent BrowserWindows like here: https://electronjs.org/docs/api/browser-window#parent-and-child-windows
You will get more easier all child windows with:
win.getChildWindows()
https://electronjs.org/docs/api/browser-window#wingetchildwindows
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360169%2felectron-event-emitter-error-while-app-quit-with-closing-all-open-renderer-proce%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It looks like what's happening is your mainWindow
close
handler gets triggered which tells other windows to close, which then fires off the window_closed
event (I guess that's a custom event that you added?), and by the timemainWindow.webContents.send
is called, the mainWindow
's close handler finished and the window closed.
Simply add an isDestroyed
check before sending the message like so:
ipcMain.on('window_closed', (e, item)=>{
if (mainWindow && !mainWindow.isDestroyed())
mainWindow.webContents.send('button_enable', item);
});
Your other options (though arguably less optimal) are:
- Set a flag when the main window is closing and have the
window_closed
handler return out if it sees the flag (surely there's no reason to send abutton_enable
message if we're about to shut everything down):
let mainWindowIsClosing = false;
mainWindow.on('close', (e)=>{
mainWindowIsClosing = true;
...
wind.close();
...
});
ipcMain.on('window_closed', (e, item)=>{
if (mainWindowIsClosing) return;
mainWindow.webContents.send('button_enable', item);
});
- You can call the
destroy
method instead ofclose
to avoid firing theclose
event for child windows. (thoughwindow_closed
isn't an Electron event I believe, so it depends on how you've hooked everything up):
mainWindow.on('close', (e)=>{
...
wind.destroy();
});
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
add a comment |
up vote
1
down vote
accepted
It looks like what's happening is your mainWindow
close
handler gets triggered which tells other windows to close, which then fires off the window_closed
event (I guess that's a custom event that you added?), and by the timemainWindow.webContents.send
is called, the mainWindow
's close handler finished and the window closed.
Simply add an isDestroyed
check before sending the message like so:
ipcMain.on('window_closed', (e, item)=>{
if (mainWindow && !mainWindow.isDestroyed())
mainWindow.webContents.send('button_enable', item);
});
Your other options (though arguably less optimal) are:
- Set a flag when the main window is closing and have the
window_closed
handler return out if it sees the flag (surely there's no reason to send abutton_enable
message if we're about to shut everything down):
let mainWindowIsClosing = false;
mainWindow.on('close', (e)=>{
mainWindowIsClosing = true;
...
wind.close();
...
});
ipcMain.on('window_closed', (e, item)=>{
if (mainWindowIsClosing) return;
mainWindow.webContents.send('button_enable', item);
});
- You can call the
destroy
method instead ofclose
to avoid firing theclose
event for child windows. (thoughwindow_closed
isn't an Electron event I believe, so it depends on how you've hooked everything up):
mainWindow.on('close', (e)=>{
...
wind.destroy();
});
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It looks like what's happening is your mainWindow
close
handler gets triggered which tells other windows to close, which then fires off the window_closed
event (I guess that's a custom event that you added?), and by the timemainWindow.webContents.send
is called, the mainWindow
's close handler finished and the window closed.
Simply add an isDestroyed
check before sending the message like so:
ipcMain.on('window_closed', (e, item)=>{
if (mainWindow && !mainWindow.isDestroyed())
mainWindow.webContents.send('button_enable', item);
});
Your other options (though arguably less optimal) are:
- Set a flag when the main window is closing and have the
window_closed
handler return out if it sees the flag (surely there's no reason to send abutton_enable
message if we're about to shut everything down):
let mainWindowIsClosing = false;
mainWindow.on('close', (e)=>{
mainWindowIsClosing = true;
...
wind.close();
...
});
ipcMain.on('window_closed', (e, item)=>{
if (mainWindowIsClosing) return;
mainWindow.webContents.send('button_enable', item);
});
- You can call the
destroy
method instead ofclose
to avoid firing theclose
event for child windows. (thoughwindow_closed
isn't an Electron event I believe, so it depends on how you've hooked everything up):
mainWindow.on('close', (e)=>{
...
wind.destroy();
});
It looks like what's happening is your mainWindow
close
handler gets triggered which tells other windows to close, which then fires off the window_closed
event (I guess that's a custom event that you added?), and by the timemainWindow.webContents.send
is called, the mainWindow
's close handler finished and the window closed.
Simply add an isDestroyed
check before sending the message like so:
ipcMain.on('window_closed', (e, item)=>{
if (mainWindow && !mainWindow.isDestroyed())
mainWindow.webContents.send('button_enable', item);
});
Your other options (though arguably less optimal) are:
- Set a flag when the main window is closing and have the
window_closed
handler return out if it sees the flag (surely there's no reason to send abutton_enable
message if we're about to shut everything down):
let mainWindowIsClosing = false;
mainWindow.on('close', (e)=>{
mainWindowIsClosing = true;
...
wind.close();
...
});
ipcMain.on('window_closed', (e, item)=>{
if (mainWindowIsClosing) return;
mainWindow.webContents.send('button_enable', item);
});
- You can call the
destroy
method instead ofclose
to avoid firing theclose
event for child windows. (thoughwindow_closed
isn't an Electron event I believe, so it depends on how you've hooked everything up):
mainWindow.on('close', (e)=>{
...
wind.destroy();
});
edited Nov 19 at 15:46
answered Nov 19 at 15:38
pushkin
3,859102551
3,859102551
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
add a comment |
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
Thanks for the simple solution. I think isDestroyed chek is the best way to solve that issue. I have tried your solution and it seems everything is ok, thanks again.
– Kerem Cavusoglu
Nov 20 at 13:57
add a comment |
up vote
0
down vote
Found a solution as follows;
mainWindow.on('close', (e)=>{
mainWindow = null;
try{
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind=>{
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
}catch(e){
console.log(e);
}
});
Before closing the main window, i set the mainwindow to null. When an info window is closed, check if its not set to null, send the mainwindow an info window is closed and its status button should be enabled;
ipcMain.on('window_closed', (e, item)=>{
try {
if(mainWindow !== null){
mainWindow.webContents.send('button_enable', item);
}
} catch (error) {
console.log(error);
}
});
I wonder, if you add aclosed
handler on themainWindow
, does it get triggered after younull
it out? Typically, you should null out the window in theclosed
handler, notclose
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate
– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
add a comment |
up vote
0
down vote
Found a solution as follows;
mainWindow.on('close', (e)=>{
mainWindow = null;
try{
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind=>{
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
}catch(e){
console.log(e);
}
});
Before closing the main window, i set the mainwindow to null. When an info window is closed, check if its not set to null, send the mainwindow an info window is closed and its status button should be enabled;
ipcMain.on('window_closed', (e, item)=>{
try {
if(mainWindow !== null){
mainWindow.webContents.send('button_enable', item);
}
} catch (error) {
console.log(error);
}
});
I wonder, if you add aclosed
handler on themainWindow
, does it get triggered after younull
it out? Typically, you should null out the window in theclosed
handler, notclose
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate
– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
add a comment |
up vote
0
down vote
up vote
0
down vote
Found a solution as follows;
mainWindow.on('close', (e)=>{
mainWindow = null;
try{
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind=>{
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
}catch(e){
console.log(e);
}
});
Before closing the main window, i set the mainwindow to null. When an info window is closed, check if its not set to null, send the mainwindow an info window is closed and its status button should be enabled;
ipcMain.on('window_closed', (e, item)=>{
try {
if(mainWindow !== null){
mainWindow.webContents.send('button_enable', item);
}
} catch (error) {
console.log(error);
}
});
Found a solution as follows;
mainWindow.on('close', (e)=>{
mainWindow = null;
try{
let openedOnes = BrowserWindow.getAllWindows();
openedOnes.forEach(wind=>{
if(wind.hasOwnProperty('custom')){
wind.close();
};
});
app.quit();
}catch(e){
console.log(e);
}
});
Before closing the main window, i set the mainwindow to null. When an info window is closed, check if its not set to null, send the mainwindow an info window is closed and its status button should be enabled;
ipcMain.on('window_closed', (e, item)=>{
try {
if(mainWindow !== null){
mainWindow.webContents.send('button_enable', item);
}
} catch (error) {
console.log(error);
}
});
answered Nov 19 at 5:52
Kerem Cavusoglu
336
336
I wonder, if you add aclosed
handler on themainWindow
, does it get triggered after younull
it out? Typically, you should null out the window in theclosed
handler, notclose
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate
– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
add a comment |
I wonder, if you add aclosed
handler on themainWindow
, does it get triggered after younull
it out? Typically, you should null out the window in theclosed
handler, notclose
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate
– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
I wonder, if you add a
closed
handler on the mainWindow
, does it get triggered after you null
it out? Typically, you should null out the window in the closed
handler, not close
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate– pushkin
Nov 19 at 18:15
I wonder, if you add a
closed
handler on the mainWindow
, does it get triggered after you null
it out? Typically, you should null out the window in the closed
handler, not close
. Your approach might prevent other window events from firing, which isn't ideal. Setting a flag like in my answer is likely more appropriate– pushkin
Nov 19 at 18:15
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
You are right. I have checked the documents again and with closed event we should set the browserwindow object to null not with the close event.
– Kerem Cavusoglu
Nov 20 at 13:59
add a comment |
up vote
0
down vote
You should use Child/Parent BrowserWindows like here: https://electronjs.org/docs/api/browser-window#parent-and-child-windows
You will get more easier all child windows with:
win.getChildWindows()
https://electronjs.org/docs/api/browser-window#wingetchildwindows
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
add a comment |
up vote
0
down vote
You should use Child/Parent BrowserWindows like here: https://electronjs.org/docs/api/browser-window#parent-and-child-windows
You will get more easier all child windows with:
win.getChildWindows()
https://electronjs.org/docs/api/browser-window#wingetchildwindows
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
add a comment |
up vote
0
down vote
up vote
0
down vote
You should use Child/Parent BrowserWindows like here: https://electronjs.org/docs/api/browser-window#parent-and-child-windows
You will get more easier all child windows with:
win.getChildWindows()
https://electronjs.org/docs/api/browser-window#wingetchildwindows
You should use Child/Parent BrowserWindows like here: https://electronjs.org/docs/api/browser-window#parent-and-child-windows
You will get more easier all child windows with:
win.getChildWindows()
https://electronjs.org/docs/api/browser-window#wingetchildwindows
answered Nov 19 at 13:47
Toinane
214
214
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
add a comment |
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
Your problem with ipcMain.on('window_closed') is because you catch also your mainWindow close hook
– Toinane
Nov 19 at 13:50
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53360169%2felectron-event-emitter-error-while-app-quit-with-closing-all-open-renderer-proce%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown