Running from source: Abnormal shutdown?

[ownedbycats]

Sometimes after running from source to test the new features and switching back to the stable version, Job Spy complains that Calibre was not shut down properly and turns off all my custom tag browser icons. Any idea why this would happen?

[chaley]

Originally Posted by ownedbycats

Sometimes after running from source to test the new features and switching back to the stable version, Job Spy complains that Calibre was not shut down properly and turns off all my custom tag browser icons. Any idea why this would happen?

No idea. I think that DaltonST needs to chime in as he knows what triggers that message. You might need to ask the question on the Job Spy thread.

You could of course not switch back. I don't unless running from source doesn't work because of incompatibilities between binary releases, which happens once in a blue moon. There isn't a significant performance difference.

[ownedbycats]

I noticed DaltonST hasn't been on for a few months. I reported a bug in Audit Log close to a month ago that usually would've been fixed by now.

I usually use stable because I have a tendency to close the console window without thinking which then closes Calibre...

[chaley]

Originally Posted by ownedbycats

I usually use stable because I have a tendency to close the console window without thinking which then closes Calibre...

I have done that.

Killing the console, therefore calibre, *is* an abnormal calibre shutdown. Could that explain what you are seeing?

[ownedbycats]

That would make sense yeah.

[ownedbycats]

Also, is it expected that any use of 'restart' (either from the menu or installing plugins) just shuts it down?

[chaley]

Originally Posted by ownedbycats

Also, is it expected that any use of 'restart' (either from the menu or installing plugins) just shuts it down?

Shuts what down?

[chaley]

Originally Posted by ownedbycats

Also, is it expected that any use of 'restart' (either from the menu or installing plugins) just shuts it down?

If you mean that 'Restart' shuts down calibre normally but it doesn't restart then yes, that is expected behavior. Hit up-arrow then return in the dos box to run calibre again.

[ownedbycats]

Yeah, it doesn't open back up until I run the batch file again.

[ownedbycats]

Also, I just figured out that I could use my minimize-to-tray shell extension and hide the console, which drastically reduces accidental closures.

[thiago.eec]

Originally Posted by ownedbycats

Also, I just figured out that I could use my minimize-to-tray shell extension and hide the console, which drastically reduces accidental closures.

I created a .bat file with this code:

@echo off
set CALIBRE_DEVELOP_FROM=path\to\calibre\src
start calibre

I put this bat on Documents folder, and made a shortcut for it on my Desktop. In this shortcut, you can right click and go to Properties > Run > Minimized.

This way you won't have a console window.

[thiago.eec]

Originally Posted by chaley

You could of course not switch back. I don't unless running from source doesn't work because of incompatibilities between binary releases, which happens once in a blue moon. There isn't a significant performance difference.

I find it way slower when opening a book on the Viewer or the Editor. If I recollect correctly, Kovid said the code is compiled on the fly in this case, which makes it slower.
As for calibre itself, it seems to work just like the normal installation.

[ownedbycats]

I did notice opening a book was slower too.