Hi Charles, thx for your feedback again.
Yeah I was thinking of just boxing the node to ensure it is visible, no searches. In a similar way to what my user category plugin does. So it would be a call to "self.gui.tags_view.model().find_item_node()" then "show_item_at_path()" or something like that.
All settings are persisted in the config file as soon as the user clicks ok in the dialog so yes everything is "remembered".
Sounds like we agree the user needs an option to disable the tag browser integration. It is just how that would interoperate with changes to the type of title search that I'm not clear about.
The simplest option would be a single checkbox that says "Show the first author in each group in the tag browser". This would take effect regardless of the type of search.
The second option would be to name it "Show the first author in the tag browser for ignore title searches". As per the name, doing anything but an author duplicate search would never manipulate the tag browser.
The third option would be to offer two checkboxes. One for "ignore title searches" and one for "title searches". We could enable/disable the appropriate checkboxes as the user switches the title match radio buttons so the user knows which is relevant.
I can't think of how a setting which changes each time you click a radio button can sucessfully work in combination with a "remembered" setting without the user wondering wtf is going on?
What did you think of the soundex - shall we let the user tune it with spinboxes or not?