View Single Post
Old 04-08-2013, 07:15 AM   #7
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,864
Karma: 13806776
Join Date: Feb 2009
Location: North Carolina
Device: Icarus Illumina XL HD, Nexus 7
Quote:
Originally Posted by kovidgoyal View Post
Oh and in case it wasn't clear, I am advocating that the current restrictions behavior become the "base" restriction, while the new feature becomes the easily switchable one. In particular, there is no need to persist the virtual library across a restart and no need for another setting to specify that a library always open with a given virtual library. Both of those are possible with the current restrictions feature, so they dont need to be duplicated.
And my idea was exactly opposite. Calling the first level a Virtual Library (as the base restriction) implementing what you suggested I think would be easier for folks to grasp than the current "Restrict to" terminology.

But as I said easy for me to speak since I won't be doing the work.
DoctorOhh is offline   Reply With Quote