Index / Archive Button Changes State on Query End

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run a query with the Index button set to Archive
2. Allow the query to complete, or change to a completed query tab and change 
back to the starting tab

What is the expected output? What do you see instead?
Expected: Index button retains selection
Current: Index button reverts back to index and does not change to archive 
without manually selecting it

What version of the product are you using? On what operating system?
RHEL6, r363(?)

Please provide any additional information below.
The Index button will change back to archive if an archive query is still 
running, but if the query completes, it will always go back to index.  This 
adds some extra clicks to continuing a search of the archived logs.

Original issue reported on code.google.com by sitko.ma...@gmail.com on 3 Aug 2012 at 1:38

[GoogleCodeExporter]

I'm open to suggestions on this.  The current behavior is intended to guard 
against accidentally submitting an archive query when you want a regular query. 
 Since archive queries are annoying to cancel (takes more clicks), the default 
was to always reset the button to "Index."  I take it you are finding it more 
annoying the other way around?

Original comment by mchol...@gmail.com on 3 Aug 2012 at 1:50

[GoogleCodeExporter]

I can see what being a problem, but at least with the way I'm using it, it 
would be nice if archive queries would automatically search the archive for 
queries started from within the results page.  So if I search a host in 
archive, click the event ID listing, I'd like to continue to filter that result 
in the archive section

Original comment by sitko.ma...@gmail.com on 3 Aug 2012 at 3:24

[GoogleCodeExporter]

Archive has been improved a fair amount since its inception, so it's probably 
time to make it more intuitive again and keep the button "sticky" to its 
setting at query time.  I'll implement this.

Original comment by mchol...@gmail.com on 3 Aug 2012 at 3:33

[GoogleCodeExporter]

Sounds good.  It doesn't have to stick across unrelated tabs, but for clicking 
buttons inside the results that spawn new tabs, it would be good to maintain 
whatever was used in that query.

Original comment by sitko.ma...@gmail.com on 3 Aug 2012 at 4:00

[GoogleCodeExporter]

This is now fixed in recent revisions.

Original comment by mchol...@gmail.com on 29 Nov 2012 at 10:38

• Changed state: Fixed