View Single Post
Old 03-17-2025, 12:06 PM   #16
DrChiper
Bookish
DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.DrChiper ought to be getting tired of karma fortunes by now.
 
DrChiper's Avatar
 
Posts: 1,029
Karma: 2003162
Join Date: Jun 2011
Device: PC, t1, t2, t3, Clara BW, Clara HD, Libra 2, Libra Color, Nxtpaper 11
Quote:
Originally Posted by Terisa de morgan View Post
YFor me, I'm using only title or author because they add an icon to the column.
No offense, but is there some reason why you do not use column coloring? It seems to me somehow easier.

Quote:
Originally Posted by Terisa de morgan View Post
You can add author For me, I'm using only title or author because they add an icon to the column. About nil variable... no idea.
I think only the true calibre gurus will be able to answer this (not for us mortals)
What I meant is this: when our template code is parsed and it evolves into a not-situation (no non-ASCII code, or no title present), then the remainder of the template code on the same code line is not further processed, and immediately the next line is processed. So when the IF statement is FALSE, any ELSE statement (when present) is executed.
I noticed this behavior when I made a mistake in the IF part and it was not noticed until I had a title which did happened to have a non-ASCII character and only then triggered the formatter on the error.

Last edited by DrChiper; 03-17-2025 at 12:10 PM.
DrChiper is offline   Reply With Quote