View Single Post
Old 11-08-2022, 03:19 PM   #46
un_pogaz
Chalut o/
un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.un_pogaz ought to be getting tired of karma fortunes by now.
 
un_pogaz's Avatar
 
Posts: 444
Karma: 672378
Join Date: Dec 2017
Device: Kobo
Quote:
Originally Posted by chaley View Post
On the other hand, the current implementation takes more menu space -- in effect two lines per search for searches that exist as bare and with children. This is the situation @ownedbycats is seeing.
Yep, but that point only comes up if you specifically create a root element. So it's easy for the user to choose between having 2 lines or slightly renaming the root to make it a child depending on what they think is most relevant to this search.

foo , foo.search1 , foo.search2 => foo.All , foo.search1 , foo.search2

This kind of small subtlety, even if it comes from constraint, are a good plus once understood.

Last edited by un_pogaz; 11-08-2022 at 03:22 PM.
un_pogaz is online now   Reply With Quote