I accept your point of view but let me speculate a bit more on this topic.
Quote:
Originally Posted by kovidgoyal
A runtime check would make a library inaccessible, when, as you correctly point out, only a few books in the library might suffer from the actual issue.
|
The inaccessibility could happen if you keep on working on
presumed path lengths but it never happens because of an effective folder moving. If you move a library, or whatever file or folder, to a not legal path (too long) Windows stops the moving operation when it meets the illegal long path. So it is impossible you succeded in moving a library or calibre at all to a too deep path through Windows.
Since it is impossible that even a single book in your library could break the chars path limit because of a folder moving, the unique case it could happen is when a user add a new book or move a library through calibre itself.
A more accurate check during these operations, and a proper message to the user, should be shown in this case and not on a hypothetical and extremely rare, too long installation or destination path.
Well the program portability involves a completely new way of thinking.
Anyway thanks for you time and kindness.
I stop bothering you on this theme don't worry
