Adding books re-arranges the list

[chaley]

Originally Posted by jhempel24

I have it sorted by Title/Author/Series/Tag so that I see say Comedy, in Author Alphabetical, if the books aren't in a sseries then they are alphabetical.

When I plug my Nook in....the books get re-arranged within Calibre.

Mea culpa.

There is a change in .18 that causes the behavior you see. To fix several ondevice display problems, I needed to refresh the GUI screen, so I did. Unfortunately, the way I did the refresh sorted by only the last sort, not the sequence of sorts. Worrying about longer sort sequences didn't occur to me, even though it should have because it was required for the sort_on_startup feature I added.

What you are seeing is the result. The display should be sorted by series, but the order of the other columns will be indeterminate. Actually, they are in DB order, but that is effectively the same thing.

I am submitting code to fix this. In the meantime, revert to .17.

[DoctorOhh]

Originally Posted by chaley

What you are seeing is the result. The display should be sorted by series, but the order of the other columns will be indeterminate. Actually, they are in DB order, but that is effectively the same thing.

I am submitting code to fix this. In the meantime, revert to .17.

Another mystery solved.

[Starson17]

Originally Posted by chaley

I am submitting code to fix this. In the meantime, revert to .17.

When Kovid adds it to the main trunk, would you post a note here, or just post the bug fix#. I'd like to fix this while running from code. Related question - do all your code mods get added to the bug list, or do you send some directly to Kovid? IOW, if I watch the bug tracker do I see all your proposed code changes?

[chaley]

Originally Posted by Starson17

When Kovid adds it to the main trunk, would you post a note here, or just post the bug fix#. I'd like to fix this while running from code.

Sure. Will post after Kovid reviews & merges (assuming he does).

Related question - do all your code mods get added to the bug list, or do you send some directly to Kovid? IOW, if I watch the bug tracker do I see all your proposed code changes?

The large majority are done without benefit of bug tracking. For a short time in the beginning I added my own bug reports and enhancement requests, but that became very boring so I stopped. I don't enter bugs fixed because of threads/posts here (such as this one), but if the OP creates a ticket then I close it properly.

The changes are all in the BZR log/repository, complete with some commentary. That would be the best place to look. I check it reasonably frequently to see what other people are up to. Kovid seems to leave the developer's name attached to the merge directives, even if he changes the code. If you use the BZR GUI, then you would need to click on a '+' circle or two until you see the string of commits you are interested in.

[jhempel24]

THANK YOU!!! I didn't think I was crazy, I knew something had to have changed...but I bow down to you for figuring this out.

[chaley]

Originally Posted by Starson17

When Kovid adds it to the main trunk, would you post a note here, or just post the bug fix#.

Fix is merged to trunk.

[chaley]

NB: Kovid is concerned that the bug fix will unacceptably reduce performance for those who don't use multi-level sorts. To deal with this, I have added YAT (yet another tweak) to limit the number of remembered sorts to apply.

Tweak documentation is:

# Set the maximum number of sort 'levels' that calibre will use to resort the
# library after certain operations such as searches or device insertion. Each
# sort level adds a performance penalty. If the database is large (thousands of
# books) the penalty might be noticeable. If you are not concerned about multi-
# level sorts, and if you are seeing a slowdown, reduce the value of this tweak.
maximum_resort_levels = 5

The code has not yet been merged, but I am confident that it will be.

[Starson17]

Originally Posted by chaley

Fix is merged to trunk.

Thanks.

[jhempel24]

so how would I implement this?

[DoctorOhh]

Originally Posted by jhempel24

so how would I implement this?

You can run from source as explained in the manual or wait for 0.7.19 to be released.

Me, I'll wait for 0.7.19

[jhempel24]

Yeah sounds like a plan, I've got no idea how to run it from source

[chaley]

Originally Posted by Starson17

When Kovid adds it to the main trunk, would you post a note here, or just post the bug fix#. I'd like to fix this while running from code. Related question - do all your code mods get added to the bug list, or do you send some directly to Kovid? IOW, if I watch the bug tracker do I see all your proposed code changes?

A new implementation of this fix has been merged to trunk. It improves general sort performance by between 3 and 5 times, and improves multi-key sort performance by up to 10 times. The bigger the database, the more the improvement.

Both the GUI and the content server use this new code.

Could those of you who run from source give it a try? I don't think anything is broken, but more use will give reassurance.

[Starson17]

Originally Posted by chaley

Could those of you who run from source give it a try? I don't think anything is broken, but more use will give reassurance.

Checking now.

[jhempel24]

So do I need to download the 7.18 again?

Thanks!!

[DoctorOhh]

Originally Posted by dwanthny

No. You can run from source as explained in the manual or wait for 0.7.19 to be released.

Me, I'll wait for 0.7.19

I know it gets confusing, they are testing it by running from source code that already has the fix in it, not by running a new version of 0.7.18. It sounds like the fix will be in the next release.