Bug with config windows not unloading if not opened, help?

[GilesSmith]

If you have a plugin with a config window, and click on it once in the plugin-tab within DemonBuddy but don't open the config window... and then quit DemonBuddy, DemonBuddy process stays running and attached to Diablo 3 and needs task-killing.

If you open the config window, and then close it, you can prevent this by doing something like

configWindow.Closed += configWindow_Closed;
private void configWindow_Closed(object sender, EventArgs e)
{
configWindow = null;
}

However if the window doesn't actually get opened, then it can't get closed, and so you can't clear the config window to prevent the process-stuck situation.

Note that this only happens if you select the plugin in the plugin list (so the config window becomes ungreyed in DemonBuddy) but DON'T actually open the config window, and then just quit DemonBuddy.

Help?

 

[sinterlkaas]

this is a old and known bug I added something for this in AntiIdle also posted this an update on for this on the configwindow example in plugins : http://www.thebuddyforum.com/demonb...ple-plugin-config-window-finally-working.html
but like I mentioned did not test this having multiple plugins running this same workaround

 

[GilesSmith]

this is a old and known bug I added something for this in AntiIdle also posted this an update on for this on the configwindow example in plugins : http://www.thebuddyforum.com/demonb...ple-plugin-config-window-finally-working.html
but like I mentioned did not test this having multiple plugins running this same workaround

Hmmm that looks like a complicated solution and I'd worry about having it on all four of my plugins, but thanks for the response. Perhaps this is a bug that needs addressing by DemonBuddy guys instead then? They need to unset the windows they created from people clicking once on the plugins without opening the config windows, or provide us with an event that we can hook onto and that actually works when DB is closed?

 

[superreeen]

If you have a plugin with a config window, and click on it once in the plugin-tab within DemonBuddy but don't open the config window... and then quit DemonBuddy, DemonBuddy process stays running and attached to Diablo 3 and needs task-killing.

If you open the config window, and then close it, you can prevent this by doing something like

configWindow.Closed += configWindow_Closed;
private void configWindow_Closed(object sender, EventArgs e)
{
configWindow = null;
}

However if the window doesn't actually get opened, then it can't get closed, and so you can't clear the config window to prevent the process-stuck situation.

Note that this only happens if you select the plugin in the plugin list (so the config window becomes ungreyed in DemonBuddy) but DON'T actually open the config window, and then just quit DemonBuddy.

Help?

void IPlugin.OnShutdown()
{
if(configWindow != null)
configWindow.Close();
}

 

[sinterlkaas]

yes I agree on that .. but this bug is in DB from the beginning and still not fixed so guess it is on there low priority list

 

[GilesSmith]

yes I agree on that .. but this bug is in DB from the beginning and still not fixed so guess it is on there low priority list

Sucks that we have to keep fixing things ourselves weeks later

 

[Kane49_2]

Sucks that we have to keep fixing things ourselves weeks later

Pretty sure they dont even know.

 

[Tony]

already fixed,you will see it on next release guys

thx for reporting

 

[sinterlkaas]

already fixed,you will see it on next release guys

thx for reporting

ah thanks for reporting as fixed now