E-viewer window size and position not remembered

[eschwartz]

I never really liked calibrePortable, you should instead try the calibrePortable that comes from portableApps. I KNOW Kovid's version of calibrePortable only works with one library at the default location.

[frank14612]

The config data location can be ascertained by going to Preferences-Miscellaneous->Open config... (the last button) open it and leave it open whilst you close calibre. Now back out to the parent folder (Alt/UpArrow) and rename the folder you came from to something like calibre.old.

Then uninstall all versions of calibre, make sure the caloibre folders in Program Files & Program Files (X86) are gone. Then install the latest 64 bit - this will be a fresh install with the welcome wizard. It will give you a fresh configuration - now tell calibre where you're library is - hopefully the window size problems will have gone - if not then

BR, I followed your instructions meticulously, yet the trouble persists without the slightest trace of a difference. In fact, it's worse now than before I started messing with it, because now even the main Calibre window won't return to the size and position I set it to, where before it was just the viewer window that wouldn't co-operate.

I have come to the conclusion that I can't use Calibre or its viewer as a daily experience anymore, as I have been used to doing for well over a year. It's too annoying now, like trying to hold open a book that keeps closing on you as you try to read it. I'll use Calibre only as a staging area for new e-books, which I will then transfer immediately to my Nook, and I'll read them there.

I don't understand what drastic thing could have happened to the program on my computer that can't be modified or undone.

I thank you for your help, regardless.


Frank

[kovidgoyal]

Run calibre in debug mode and it might print out something that will tell us what the problem is on your computer. Right click the preferences button and select restart in debug mode and post the debug log.

[frank14612]

Following Kovid's post,

1. I uninstalled Calibre 1.9 64-bit.
2. I installed Calibre 1.9 32-bit.
3. I started Calibre up, then switched to debug mode as advised by Kovid.
4. I adjusted the size and position of the Calibre window.
5. I opened an e-book and adjusted the viewer window size and position, font, and other niceties.
6. I opened about 6 e-books in succession.

Everything worked beautifully! The program window and the viewer window size and position, etc., were all remembered precisely.

7. I closed Calibre then opened the debug file described by Kovid. Here are the contents:

calibre Debug log
calibre 1.9 isfrozen: True is64bit: False
Windows-7-6.1.7601-SP1 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '7', '6.1.7601')
Python 2.7.5
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
Starting up...
Started up in 23.17 seconds with 494 books
Worker Launch took: 1.50900006294
Worker Launch took: 0.260999917984
Worker Launch took: 0.248999834061
Worker Launch took: 0.286999940872
Worker Launch took: 0.253000020981
Worker Launch took: 0.323999881744

8. I reopened Calibre in normal mode. The program windows size and position I had set were remembered!
9. I then opened 6 different e-books in succession.

Again, everything worked beautifully! The program window and the viewer window size and position, font, etc., were all remembered precisely.

I am dumfounded! I am happy that everything is working normally again, and am embarrassed that everything seems to be fixed now, when I didn't do anything other than uninstall the 64-bit version of Calibre and reinstall the 32-bit version. Could running in debug mode have fixed the problem?

Whatever the reason for the fix, I am happy and pleased with Calibre once again. It's like getting an old friend back!

My thanks to RB and Kovid for their attention to my plea for help and getting me back to the pleasurable use of this fantastic program!


Frank D

[eschwartz]

Originally Posted by eschwartz

I never really liked calibrePortable, you should instead try the calibrePortable that comes from portableApps. I KNOW Kovid's version of calibrePortable only works with one library at the default location.

Apparently I was wrong about this, someone on another thread kindly pointed out that about a year ago this was fixed and I never noticed.

[theducks]

Portable STARTS UP with the default location always the same.
You can then switch to ANY valid Library, even if it is on your local disk or another thumb drive (as long as the Calibre Portable remains plugged in )

[eschwartz]

Oh, so it doesn't really work right?

Portableapps version works perfectly as if it was installed, then just migrates those settings to another computer. It will start up with your last used library, wherever, through the magic of PAL

[theducks]

Originally Posted by eschwartz

Oh, so it doesn't really work right?

Portableapps version works perfectly as if it was installed, then just migrates those settings to another computer. It will start up with your last used library, wherever, through the magic of PAL

Calibre portable works perfectly Right.
Right being 'Works as Advertised'.

It is your definition that is off.

[BetterRed]

Originally Posted by frank14612

I am dumfounded! I am happy that everything is working normally again, and am embarrassed that everything seems to be fixed now, when I didn't do anything other than uninstall the 64-bit version of Calibre and reinstall the 32-bit version. Could running in debug mode have fixed the problem? Frank D

@frank14612 that's great, and thanks for letting us know the final outcome.

I doubt that running in debug would have contributed to the solution, although I'll bow to Kovid's opinion on that. But replacing 64 bit with a 'fresh' 32 bit has been known to solve other problems for no apparent or good reason, generally these have been related to the file system.

What prompted you to try a fresh 32 bit. I thought of suggesting it but after my other shot in the dark didn't do the trick... I thought better not

Perhaps that nature of your problem will give the developers or others a hint as to the underlying reason why this occasionally happens. Its got me baffled too.

Cheers BR

[kovidgoyal]

@escwartz: calibre portable will startup with the last used library, if the last used library is inside the calibre portable folder. Otherwise it will always start up with the default portable library.

[eschwartz]

Originally Posted by kovidgoyal

@escwartz: calibre portable will startup with the last used library, if the last used library is inside the calibre portable folder. Otherwise it will always start up with the default portable library.

I see. That sounds reasonable. I think I'll just stay with the Portableapps version, though, since I have been grandfathered in.

[BetterRed]

I just got reminded that I can consistently get calibre not starting with the last screen position

If I start calibre and immediately - i.e. before calibre starts to paint its window (I don't show the startup splash), give focus to an already running application then calibre will paint itself into a position where its about half off both the right and bottom edges of the monitor.

Some time in the past I may have dragged calibre into that position to get partially it out of the way - but that wasn't where it was last time I closed calibre - it was weeks/months/years ago

I'm posting this for the benefit of developers because, for me at least, its consistent and it may give them a clue as to what might have created frank14612's original problem.

This is not a recent phenomena, can't say when I first noticed it, maybe it's been there 'forever' - ie since I started using calibre in late 2011.

BR

[frank14612]

Originally Posted by BetterRed

@frank14612 that's great, and thanks for letting us know the final outcome.

You're welcome!

What prompted you to try a fresh 32 bit. I thought of suggesting it but after my other shot in the dark didn't do the trick... I thought better not

A sense that "returning to basics" might be the best approach when having absolutely no idea of what to do to return to a prior state of stability (i.e., just a feeling).

Perhaps that nature of your problem will give the developers or others a hint as to the underlying reason why this occasionally happens. Its got me baffled too.

If this helps others by serving as an example, I'm happy.

Frank

[theducks]

Frank
if you have done a 'Uninstall' of the 64 bit version using Windows control panel, now go check the 'Program Files'\ (not 'Program Files (x86)' Calibre2 for remnants (there should be none, those probably were the problem) :delete the Calibre2 folder

[frank14612]

Originally Posted by theducks

Frank
if you have done a 'Uninstall' of the 64 bit version using Windows control panel, now go check the 'Program Files'\ (not 'Program Files (x86)' Calibre2 for remnants (there should be none, those probably were the problem) :delete the Calibre2 folder

Ducks,

I just checked, and there is no Calibre2 folder in the Program Files folder (i.e., the 64-bit program folder). That's because I used IObit Uninstaller (http://www.iobit.com/advanceduninstaller.html) to uninstall the program, not Windows' own uninstaller. IObit removes every last bit of the program including all registry entries, etc. That way there are no worries about something being left behind that will come back and cause problems later. Thanks for the follow-up!

Frank