Using the Search (Ctl-F)

[Paul Abrahams]

On Wednesday, April 06, 2011 07:10:24 PM Leigh Honeywell wrote:
> On 11-04-06 04:20 PM, Paul Abrahams wrote:
> > The Description option for a search has a button "Case Insensitive?". 
> > But how do I indicate whethe r the search is or is not case insensitive?
> >  I'd expect something that says "Case Insensitive" with no question
> > mark, a check box, or something like that.  As it is, I can't tell the
> > state of the insensitivity test.
> 
> I just sent in a patch to fix this, because it should be a checkbox not
> a button.  For now, the button is depressed by default which makes the
> search case insensitve.  If you want to make it case sensitive, press it
> and that will turn it off.  Counterintuitive, I know :)  Here's the
> bugreport, for your reference:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=602052
> 
> I agree with bcr at wt.net that the checkbox meaning should be inverted,
> and will be fixing that in the next few weeks when I learn a bit more GTK.
> 
> > Also, the Find Transactions window offers four options: New Search,
> > Refine Current Search, Add Results to Current Search, and Delete Results
> > from Current Search.   However, once the search has been activated, the
> > Find Transactions window disappears, offering no way I can see to modify
> > the search.  So how, for instance, would I refine the current search if
> > the Find Transactions window is now closed?
> 
> I haven't found this to work either.  Here's an applicable bug report:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=361285
> 
> > The answers to these questions ought to be obvious, but I seem to have
> > missed them.
> 
> It's not just you in this case, don't worry.  There's a fair bit of work
> to be done on search stuff, and I'm going to put some coding time into
> it over the next couple of months.  I would really appreciate, if you
> have the time, that you file bugs for these issues in the bugtracker -
> preferably with the word "search" somewhere in the bug name so that I
> can find them easily.

I've just created two bug reports, #646975 and #646976, as you requested.

Paul