Quote:
Originally Posted by JimmXinu
Known Issues:
- Sort depth: Calibre limits how many sort columns it applies to 4 by default when apply_state() is called and at Calibre startup--not sure how I never noticed that before. But we can pass in a bigger value. This version saves and applies all sorted columns. Perhaps VM should be similarly limited instead?
|
This limitation was one of the prime reasons why I started using VM.
Quote:
Originally Posted by JimmXinu
- Also, it looks like Calibre forces Date aka timestamp(desc) into the sort order if not already included, either adding it or replacing the last(least precedence) sort item. Is this a concern or continue to ignore?
|
I think this explains, in part at least, why I was getting what I regarded as bizarre behaviour in June of last year when you implemented some other changes, IIRC they were VM related.
As you may recall, because the changes you implemented back then didn't really interest me, I decided to stick with version 1.3.2. I don't use Split View, but before upgrading to calibre 3.17 I did do some tests to ensure it didn't interfere with my usage of the old VM, which it didn't. When you release the new version I'll reconsider my decision of June 2017, my preference always is to be using current versions - assuming it doesn't involve any monetary considerations.
BR