View Single Post
Old 04-14-2021, 09:20 AM   #533
capink
Wizard
capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.capink ought to be getting tired of karma fortunes by now.
 
Posts: 1,203
Karma: 1995558
Join Date: Aug 2015
Device: Kindle
Quote:
Originally Posted by chaley View Post
A thought: both the basic scope manager and the selection modifier support searching, but with different options. They also have options that appear to do the same thing. Perhaps the visual presentation and option descriptions should be made the same?
They do have the same functionality. I will try to make them look as close as possible. However, there are some differences between "Basic Scopes" and "Selection Modifier". One thing is that "Selection Modifier" can only select books within the confines of the current view (virtual library + current search), so I have to give users the option to change this (clear virtual library, clear search ... etc). Basic scopes is not bound by the current view in the library, although it has an option to respect the current virtual library.

Another limitation of the Selection Modifier is that the search entered by the user has to be validated or else the settings dialog will print an error message. This is done because if the user combines a search with the option to select all books in current view, and the search turns out to invalid, all books in current view (the whole library most likely) will be selected and acted upon by subsequent actions.

The above point is whey I had to introduce the "Search Using Templates" as separate action because the search cannot be validated ahead of time as required by the selection modifier validator, since it results from a template that can only be evaluated at runtime

I didn't have to bother with search validation in Basic Scopes, because if the user enters an invalid search it will simply return an empty book ids list, with no harmful consequences.

Quote:
Originally Posted by chaley View Post
Or perhaps embed the scopes dialog into the selection modifier, replacing the search part? If you did this then you wouldn't need to add "scopes" to the selection modifier because they would be built into it.
I was thinking more about converting "Template Scopes" into selection (as in the template I posted for @Terisa de May) because everything you can do with Basic Scopes you can already do with the Selection Modifier, except for the book vars option.

But your point made me realize that I can modify the "Search Using Templates" action to actually make it use and call "Template Scopes", thus removing the need to add an option to the selection modifier.
capink is offline   Reply With Quote