Allow for an instance of steam-limiter to temporarily disable an existing instance

[GoogleCodeExporter]

This is a prerequisite for cleanly supporting a "portable" version of the 
limiter which can be run with an in-folder configuration not just separate from 
but alongside a regularly installed version.

This mechanism would require the pre-existing copy of steam-limiter to close 
its window and unload its filter if currently loaded; once close, to resume 
itself it will monitor a process ID, and when that process ID exits the filter 
instance can resume itself.

A minor advantage of supporting such a mechanism is also making it easier in 
development to test a new filter build while leaving the previous stable 
version in place - useful to me, if no-one else, because I actively use the 
filter as well as develop it.

Original issue reported on code.google.com by nigel.bree@gmail.com on 15 Dec 2011 at 10:43

• Blocking: #10

[GoogleCodeExporter]

Original comment by nigel.bree@gmail.com on 15 Dec 2011 at 10:44

[GoogleCodeExporter]

Implemented in the v0.5 release, will close after more testing

Original comment by nigel.bree@gmail.com on 20 Dec 2011 at 11:37

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by nigel.bree@gmail.com on 1 Feb 2012 at 9:10

• Changed state: Verified