Quote:
Originally Posted by kovidgoyal
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.
|
Sorry, don't quite follow.
Assuming we use your suggestion and add virtual libraries to the library menu: what is the relationship between
- a virtual library and the current preferences -> behavior -> restriction at startup?
- what is in the restrictions box and the current preferences -> behavior -> restriction at startup?
- what is in the restrictions box and the virtual library menu?
Currently a startup restriction is shown in the "restrict to" box. That means that the startup restriction can (and does) go away frequently, which tells me that it is not a "virtual library". Are you suggesting that the startup restriction no longer populate that box, but instead be added (somehow) to the virtual libraries that the user can choose from?