"Choose what happens before" issue about displaymagician HOT 4 CLOSED

Thanks @stringfieldmark . I've been away for the last few days but will take a look at this in the next day or two. I'm wondering if some of the recent changes I made for unlimited program starts had an effect on this, as it was working back when I built that functionality in. It's possible I missed copying a setting across or something like that. I'll take a look and check.

By the way, thank you for an excellent bug report. It's very clear to me now the area of the codebase I need to look at, so your clear report really helps. I'm going to make it an example of a 'good first issue'!

Thanks
Terry

from displaymagician.

Ok. I've fixed that issue in develop branch, but will be rolling that out in v1.1.2 which will be about 3 weeks away. The reason for this is that I've been rolling out so may fixes that I think people will be getting annoyed with the number of times they need to update. I'm trying to make it 2-3 weeks between releases now, and to roll a few more features into each release.

Another edge case I found is that some start programs spawn different processes from the one that we started, and that means that I needed to figure out a way to discern this. I've done so now, so it should even close the children of the parent process if its a direct launcher. I haven't yet written logic to walk the process tree to individually close each process as that seems a tad excessive at this point. I'll wait for more feedback from the userbase before heading down that path.

from displaymagician.

from displaymagician.

@stringfieldmark The fix for your issue you submitted is in DisplayMagician v1.1.2 I released today.

I've also added GOG.com launcher support, and Epic Games launcher support because it turned out they were pretty easy to develop :).

from displaymagician.