View Single Post
Old 01-22-2025, 02:24 AM   #51
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: 446
Karma: 672378
Join Date: Dec 2017
Device: Kobo
When I first saw the icon rule viewer, displaying the internal value assosiated to template bothered me a little because it wasn't {template} and so is wasn't consistent with other locations when a template is used to generate value. It really stuck in my mind for a while, but I couldn't find a way to write a good code to proposal.
Here my suggestion: Since the column "Use for children", write then a text {template}.

...
And now that I think about it, maybe it would be better than the internal value TEMPLATE_ICON_INDICATOR use " {template} " has value directly rather than " template " as is currently the case. Hm, it broke a bit if the user and test the feature on preview, but it's the risk of using preview and it will better display the fact that this icon rule is a template generator (instead that my suggestion above).

Last edited by un_pogaz; 01-22-2025 at 02:37 AM.
un_pogaz is offline   Reply With Quote