Thread: New to Calibre
View Single Post
Old 08-22-2014, 06:08 PM   #3
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,635
Karma: 29710510
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by theducks View Post
usually: 1 of 2 things can cause this
1) you have 2 instances of Calibre running (eg 32bit and 64 bit), the last closed saves positions.

2) you have a permissions problem with your configuration folder that prevents (I would expect ALL calibre UI ) settings being saved.
@theducks - re 1 - by design you can only run the one instance of calibre at a time, and by default the 32 and 64 bit versions share the same config data.

@ferretman - Calibre does not have a "Save Layout" feature as such, it saves the current state on exit and restarts with it.

I think the layout data (window sizes, column widths etc) is written to gui.py and/or gui.json in the config folder when the program is closed. If you watch the modify dates on those files while you start calibre, change something and exit calibre then the modify dates should change.

If not then - why not? Ensure they are not read only and they are not permission restricted, although I would expect either of those conditions to generate some sort of error.

BR
BetterRed is offline   Reply With Quote