View Single Post
Old 04-08-2013, 06:52 AM   #2
DoctorOhh
US Navy, Retired
DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.DoctorOhh ought to be getting tired of karma fortunes by now.
 
DoctorOhh's Avatar
 
Posts: 9,897
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Kindle PaperWhite SE 11th Gen
Being able to set a restriction to a already set virtual library may come in handy and seems to be a natural extension of the feature.

I always have my library open to a restricted view and possibly if working on a project having a persistent 2nd level restriction might be of use. Possibly changing the first restriction from Restrict to to Virtual Library (I think naming the dropdown list Virtual Library would be more descriptive of its use) and have the second level restriction referred to as Restrict to or Restricted view.

As long as you find value in this I do not think it increases the complexity of this feature beyond its current level.

It is one of those things I may not use often but will be nice to have when the urge hits me. Looking forward to changes you may implement.

Last edited by DoctorOhh; 04-08-2013 at 06:55 AM.
DoctorOhh is offline   Reply With Quote