[BetterRed]

Originally Posted by BookJunkieLI

I still need to do a little playing, because I only noticed it just before I had to leave for work this morning, but it looks likes VM's search restriction does work in 2.19, and everything prior to that, but only if you open a virtual library and close it before you select a View with a search restriction. Plus I think you need to do it with every new session. That's what I need to play with. The other option seems to be to do a Restore Database every time you open the library and, well, that's not gonna happen.

Without going all the way back to 2.0 I can't say for sure, but I wouldn't be surprised this if is a QT5 quirk because I know it's not an issue in 1.48. I use that pretty much every day at work and haven't had any issues with VM.

See if this helps - https://www.mobileread.com/forums/sho...0&postcount=12

I think I was able to recreate your 'problem' on 2.19 and 1.48 by creating a View (Test) with a saved search, which worked as expected. But when I switched back to my Default view the saved search was still in force

So I ticked the Apply Save Search in the Default view settings but left the drop down blank. Voilà , if I switched from a view with a saved search, to one without, then no saved search was applied

I tested it with and without an active VL, seemed to work in both situations. I imagine you'd get similar behaviour with a Search Restriction as I got for Saved Search.

But the post I refer to above predates the existence of virtual libraries and Qt5, which makes me wonder if your VM settings at home and at work are the same, particularly regarding the Apply <search> settings.

I'm also wondering what purpose the check boxes actually serve, maybe all that's need are the values, where 'empty' means don't apply any search constraints.

BR