GUI should change Start button to Stop after benchmark is started

[GoogleCodeExporter]

To reproduce, click the Start Benchmark button on OS X.

It would be nice to see the button change to Stop Benchmark. Clicking it would 
stop the currently 
running benchmark and change the button back to Start Benchmark.
Instead, currently, the Start Benchmark button is merely disabled. Currently, 
the only way to stop 
the benchmark is to quit the program, but this means that if you want to run 
another benchmark, 
you must launch the program again.

I am using namebench 1.1 on OS X

This is a followup to Issue 21, and an extraction of Issue 21 Comment 1 (by 
beerlingtonvt) into an 
issue of its own. This probably should be marked Type-Enhancement and 
Priority-Low, but I don't 
see a place for me to do that.

Original issue reported on code.google.com by roryookane on 18 Jan 2010 at 9:07

[GoogleCodeExporter]

Original comment by thomas.r...@gmail.com on 26 Jan 2010 at 8:50

• Changed state: enhancement

[GoogleCodeExporter]

Original comment by thomas.r...@gmail.com on 26 Jan 2010 at 8:51

• Changed title: GUI should change Start button to Stop after benchmark is started
• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

denj

Original comment by melissou...@gmail.com on 27 Jan 2010 at 12:30

[GoogleCodeExporter]

What would be the point of stopping the current benchmark run?  You means you 
want the 
ability to continually stop a benchmark start a new one stop that one start a 
new one 
stop that one .... pointlessly?

Original comment by khurtwilliams on 23 Feb 2010 at 1:49

[GoogleCodeExporter]

No, I want to be able to change my mind about the settings for the benchmark 
test
while the test is running, and restart the test. For instance, if I want to add
another nameserver to test, or if I accidentally left the menu to use my Firefox
bookmarks even though I use Safari. Or maybe I'm on a laptop and just about to 
leave
an area with wireless, and I want to stop the test manually rather than watch 
it try
uselessly and then fail after I go out of range, and rather than quit the 
program and
have to re-configure the settings for the test when I relaunch namebench. 
Though the
scenario with the bookmarks source is what actually happened to me to prompt 
this
suggestion.

Original comment by roryookane on 14 Mar 2010 at 9:30