MobileRead Forums - View Single Post - Calibre Book Editor - "Previous" button under text search not working

VirgoGirl · 05-30-2019, 08:05 PM

Hi! This is a minor, yet annoying issue I just noticed today.

I had been running Calibre 3.18.? 64-bit version on Win 10 using Calibre's book editor, and noticed that I couldn't go pack to a previous "hit" using the "Text Search" feature. I *thought* I had been able to do that prior to today, I can't honestly remember. Not being able to do it on ANY epub, I updated to 3.43 (the latest version as of tonight), same problem. I can search "down" with the "next" button, but If I try and go "up" with the "previous" button, it'll find one hit then nothing, even if I found 12 things going "down".

Is this a bug? Or maybe did Win 10 kill something (again)? Or, am I just crazy and this is the way it's always worked?

Sorry to be a pain, I'm just trying to figure out if I'm crazy.

Update: Just double checked, after finding one hit using "down", it won't find a "previous" hit. At all.

05-30-2019, 08:05 PM	#1
VirgoGirl "Why is it doing that?" Posts: 322 Karma: 725344 Join Date: Sep 2011 Device: Black Kobo Touch & Glo, responsible for 2 PaperWhites	Calibre Book Editor - "Previous" button under text search not working Hi! This is a minor, yet annoying issue I just noticed today. I had been running Calibre 3.18.? 64-bit version on Win 10 using Calibre's book editor, and noticed that I couldn't go pack to a previous "hit" using the "Text Search" feature. I thought I had been able to do that prior to today, I can't honestly remember. Not being able to do it on ANY epub, I updated to 3.43 (the latest version as of tonight), same problem. I can search "down" with the "next" button, but If I try and go "up" with the "previous" button, it'll find one hit then nothing, even if I found 12 things going "down". Is this a bug? Or maybe did Win 10 kill something (again)? Or, am I just crazy and this is the way it's always worked? Sorry to be a pain, I'm just trying to figure out if I'm crazy. Update: Just double checked, after finding one hit using "down", it won't find a "previous" hit. At all.