View Single Post
Old Yesterday, 08:53 AM   #64
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 22,409
Karma: 31000056
Join Date: Mar 2012
Location: Sydney Australia
Device: none
I understand exactly what I am doing.

I am pressing a now similarly named button in two calibre plugins that change the same calibre setting that is ordinarily accessed via this:

Click image for larger version

Name:	Screenshot 2026-02-23 233052.jpg
Views:	8
Size:	81.5 KB
ID:	221310

Which is stored in the calibre configurations, here:

Click image for larger version

Name:	Screenshot 2026-02-23 233945.jpg
Views:	8
Size:	108.3 KB
ID:	221311

If software was object oriented we wouldn't be having this exchange, because the 'button' in all three places would be instantiations of the same UI element operating on the same data item - but that holy grail of the 1970s has long flown the coop… coffee and pasta won the game

BR
BetterRed is offline   Reply With Quote