CC alpha release 3.4.4c

[chaley]

Originally Posted by Purple Lady

I sent the logs and noticed something very interesting on the Calibre log searching for one of the sent books. Do you know how a date in 2015 can be set? I guess this book will be sent every time I connect with the sync flag set unless I can figure out how to change it.

SMART_DEV (82982.66: 0.000) _check_if_format_send_needed Parable of the Sower cal_mtime 2015-05-14 05:34:59.634357+00:00 cc_mtime 2014-09-13 19:02:36-04:00

I have changed calibre to refuse to sync books with future dates. The change will be source today and in the next release.

Calibre asks CC to show a "toast" (popup message) if this happens. It also shows a dialog with the list of titles affected.

BTW: I think you can reset the date of these files by opening them with the book editor, erasing a character somewhere, adding the character back, and then saving the file.

[Purple Lady]

Originally Posted by chaley

I have changed calibre to refuse to sync books with future dates. The change will be source today and in the next release.

Calibre asks CC to show a "toast" (popup message) if this happens. It also shows a dialog with the list of titles affected.

BTW: I think you can reset the date of these files by opening them with the book editor, erasing a character somewhere, adding the character back, and then saving the file.

I'll have to look at the dates when I get home. I connected wirelessly this morning and it didn't try to send the books again. It did send the covers though.

Is the future dates also the cause of the looping?

[chaley]

Originally Posted by Purple Lady

Is the future dates also the cause of the looping?

Yes. Because the book is future-dated, the mod time of the book file is always later than the mod time of the device file. That situation didn't occur to me.

[kaufman]

Originally Posted by chaley

Yes. Because the book is future-dated, the mod time of the book file is always later than the mod time of the device file. That situation didn't occur to me.

That's interesting. When you copy a book to the device, you don't set the mod time on the device to the value on the computer?

[chaley]

Originally Posted by kaufman

That's interesting. When you copy a book to the device, you don't set the mod time on the device to the value on the computer?

No. It is set to the time on the device. When calibre sends a book the device driver does not have access to the book file or the database, and cannot know its mod time.

[kaufman]

Originally Posted by chaley

No. It is set to the time on the device. When calibre sends a book the device driver does not have access to the book file or the database, and cannot know its mod time.

That makes sense.

By the way, I am still getting the behavior where pressing the back from the author grouping will reshow the author grouping. This repeats a couple of times, and then it usually goes to the ungrouped screen. Sometimes when I hit back it opens the grouping drawer, and sometimes it shows the details screen of a book.

It doesn't always do this, but I haven't figured out yet what I am doing to get it into this state.

I am still trying to track it down.

[Purple Lady]

Originally Posted by kaufman

That makes sense.

By the way, I am still getting the behavior where pressing the back from the author grouping will reshow the author grouping. This repeats a couple of times, and then it usually goes to the ungrouped screen. Sometimes when I hit back it opens the grouping drawer, and sometimes it shows the details screen of a book.

It doesn't always do this, but I haven't figured out yet what I am doing to get it into this state.

I am still trying to track it down.

I noticed this as well, but I thought that was fixed for me in 3.4.4b

[kaufman]

Originally Posted by Purple Lady

I noticed this as well, but I thought that was fixed for me in 3.4.4b

Well, I am sorry you are getting this, but glad to know I am not going crazy.

FWIW, I did 3.4.4c as a clean install, so this is not an upgrade issue.

[chaley]

Originally Posted by Purple Lady

I noticed this as well, but I thought that was fixed for me in 3.4.4b

Originally Posted by kaufman

Well, I am sorry you are getting this, but glad to know I am not going crazy.

FWIW, I did 3.4.4c as a clean install, so this is not an upgrade issue.

The back button in Android is a catastrophe waiting to happen. There are no standards for how it is to work. Android itself adds things to the "back stack". Different Android versions and different versions from vendors do different things. All in all, it makes it very hard to debug.

[kaufman]

Originally Posted by chaley

The back button in Android is a catastrophe waiting to happen. There are no standards for how it is to work. Android itself adds things to the "back stack". Different Android versions and different versions from vendors do different things. All in all, it makes it very hard to debug.

Sorry for the hassle. If it helps at all, I don't remember this ever happening before 3.4.4a or 3.4.4b.

[chaley]

Originally Posted by kaufman

Sorry for the hassle. If it helps at all, I don't remember this ever happening before 3.4.4a or 3.4.4b.

And there was no change at all to what gets put on the back stack for more than a year. That isn't to say that you aren't having the problem, only to say that the problem must have been there for a long time.

Either that or it was introduced by a system upgrade, which brings up the question. Is anyone other than a Samsung user seeing problems with back?

[jackie_w]

Originally Posted by chaley

Either that or it was introduced by a system upgrade, which brings up the question. Is anyone other than a Samsung user seeing problems with back?

I'm a Samsung-only user and I'm not aware I'm having back-button problems So, either I'm not having them or it's something I'm tuning out because I don't care enough. Is there a detailed description posted of the erroneous behaviour.

[kaufman]

Originally Posted by chaley

Either that or it was introduced by a system upgrade, which brings up the question. Is anyone other than a Samsung user seeing problems with back?

I just checked and my last software update was 5/13/2014 or 13/5/2014. I'm pretty sure this didn't show up for me until 3.4.4a or b. But, its possible I just hadn't hit the conditions yet.

Originally Posted by jackie_w

Is there a detailed description posted of the erroneous behaviour.

Lets say you are looking at the detail for a book. You click on the author and that author's books are displayed. You then click on one of the books to go to that book's details. At that point, the back button is supposed to follow the path of:

Book Details->Authors: XXX, YYY->Authors->No Grouping

Instead, CC sometimes gets stuck in a loop of constantly reshowing author. Or it will start jumping to the details for books that might have been previously opened. Once in a while it will display a blank page. The problem doesn't happen every time.

I have been trying to track down what I am doing to make it happen, but so for no luck.

[jackie_w]

That might explain why I haven't noticed any errors. I have hardly ever clicked a link inside Book Details. Nevertheless this is what happens when I do it now:

• Open book list - no grouping
• Open book details for Joe Abercrombie - The Blade Itself
• Tap hyperlink for Joe Abercrombie
• 3 books by J.A. displayed in booklist. Group drawer has Authors - A - Joe Abercrombie selected
• Open book details for Joe Abercrombie - Before They Are Hanged
• Hit back button - shows me 3 J.A. books in booklist
• Hit back button again. Shows me all books in book list. Group drawer displays expanded Authors (by first letter), no item selected
• Hit back button again. Book list still shows all books. Group drawer back to No Grouping.

I don't think there was any unexpected behaviour here.

[kaufman]

Originally Posted by jackie_w

That might explain why I haven't noticed any errors. I have hardly ever clicked a link inside Book Details. Nevertheless this is what happens when I do it now:

2 things:

1) I'm not sure you have to follow the exact path I gave. I was just giving one example. It may not have anything to do with tapping on the link in a book. I'm still not sure exactly how I make it fail, that was just supposed to be an example of the behavior I was describing. Sorry if I wasn't clear.

2) It doesn't always fail. It doesn't even usually fail. I have spent the last half hour trying different thing to make it fail (trying things while connected, leaving the program and then coming back in, large amount of book hopping, etc) and I haven't made it fail once. On the other hand, it failed earlier this morning and once last night.