Thread: Weird Column behavior with new update
View Single Post
Old 09-20-2014, 04:52 PM   #20
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: 21,893
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by Gladtobemom View Post

changed all three files to .save

BTW, I noticed that NEW files are being created with those file names in the Appdata/calibre directory.

Please note that initially, this time it popped into paged-3 column correctly, but when I activated the table of contents and then closed it, that's when wonky stuff started happening.
@Gladtobemom - sorry, re the third file rename - my eyes saw three parts (viewer_themes.json) and assumed all was in harmony. And, I should have mentioned the files would be recreated - calibre's funny that way

Aaah, I can reproduce the behaviour in version 2.3 if I futz with the TOC.

However, if I view the same mobi in version 1.48 or 2.00 I cannot reproduce the behaviour (using the same viewer.json, viewer.py and viewer_themes.json files). So it would appear that something changed between 2.0 and 2.3. One thing I noticed in 2.3 is that I can slide the right edge of the TOC pane beyond the last character of the longest TOC entry, can't do that in 1.48 and 2.00.

BR
Last edited by BetterRed; 09-20-2014 at 07:37 PM.
BetterRed is offline   Reply With Quote