"Restrict to" criterion sticks after it's been cleared

Changing the component for this bug.

 assignee cbhaley
 status triaged

To understand, you are setting the restriction to 'current search' when the current search is empty, which leads to the restriction being "stuck"? You can avoid this problem by setting the restriction to the empty value (top of the list) instead of an empty search. If you have already set it to an empty search, which you must have done if the restriction is "stuck", then you can unstick it by setting it to the empty value again.

Submitted a fix for the problem where setting the restriction to an empty current search clears the restriction box but does not clear an existing restriction.

Fixed in branch lp:calibre. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased

OMG, I'm an idiot. Yes, as you supposed, I was selecting "*Current Search" while the current search was empty, and I was puzzled by the lack of response. I thought my only two choices were the "No News" search that I'd created and the "*Current Search" that is present by default. I didn't notice that there was also an empty field in the drop down menu.

Of course, I see the empty value now that you've pointed it out to me, and it works great! Sorry for the trouble. And thank you for an amazing application.

Kevin

> From: Charles Haley <email address hidden>
> Subject: [Bug 871921] Re: "Restrict to" criterion sticks after it's been cleared
> To: <email address hidden>
> Date: Tuesday, October 11, 2011, 12:40 AM
> To understand, you are setting the restriction to 'current
> search' when the current search is empty, which leads to the
> restriction being "stuck"? You can avoid this problem by
> setting the restriction to the empty value (top of the list)
> instead of an empty search. If you have already set it to an
> empty search, which you must have done if the restriction is
> "stuck", then you can unstick it by setting it to the empty
> value again.
>
> Submitted a fix for the problem where setting the
> restriction to an empty current search clears the
> restriction box but does not clear an existing restriction.
>
> ** Changed in: calibre
> Status: Triaged => Fix
> Committed
>
> --
> You received this bug notification because you are
> subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/871921
>
> Title:
> "Restrict to" criterion sticks after it's been
> cleared
>
> Status in calibre: e-book management:
> Fix Committed
>
> Bug description:
> I have a saved search called "No News": ( not tags:"=News").
> I use it in the "Restrict to" drop-down menu. Selecting it
> hides news items from the active view. So far so good.
> Deselecting it -- i.e., selecting *Current Search in the
> drop-down menu --should restore news items to the active
> view. However, they remain hidden. The only two ways I've
> discovered to bring them back is to wait for the news
> recipes to be fectched again, or switch to a different
> library and back again (while keeping "No News" deselected,
> of course). I hope you can repeat this behavior. Otherwise,
> I'm stumped. :-)
>
> v.0.8.21, Windows XP
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/calibre/+bug/871921/+subscriptions
>