View Single Post
Old 09-20-2010, 02:04 PM   #63
Starson17
Wizard
Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.Starson17 can program the VCR without an owner's manual.
 
Posts: 4,004
Karma: 177841
Join Date: Dec 2009
Device: WinMo: IPAQ; Android: HTC HD2, Archos 7o; Java:Gravity T
Quote:
Originally Posted by chaley View Post
It wouldn't be hard to provide a tweak that would make all the history comboboxes case sensitive. It would be much more if a bother to do them individually. Boxes where it really should work one way or the other (like S/R) could set the behavior explicitly.
Up until now, I have had very few situations where I want case sensitive regular searches. I would not want a tweak to set it permanently, but OTOH, I wouldn't mind having to jump through a hoop or two to get that capability for the few times I need it for the search (however, see below). I don't have any need to save a case sensitive search, but just a box to turn it on/off would be fine, even if that box was hidden in the Advanced dialog).

Quote:
I have finished the latest effort and submitted it to Kovid. The attached screen shot shows what it looks like in regexp mode. In character mode the 'destination' line of controls goes away. You will see that I did not do general templates, but instead provide for explicit source and destination fields. Handing multiplicity was simply too hard in the template case.
It really looks great to me. It's exactly what I had in mind, with a bit extra. I doubt I'll miss having general templates.

On the case sensitivity issue for general searching, the fact that S&R can do case sensitive searches will actually make it more likely that I'll want case sensitive regular searches.
Before running a regex in S&R, I've been running it in the regular search. It helps give me a better idea of what odd cases may crop up in a case sensitive S&R before actually committing to it. It also helps give me more control over the selected files that the S&R will be applied to. There's no point in selecting more books for the bulk metadata edit than you know need to get changed. Without case sensitivity in regular searches, you may have to select all books, even if you only want to change some that have a certain case problem in the fields.

(Last - congrats on getting the new custom column release into beta. I hope to look it over soon.)
Starson17 is offline   Reply With Quote