If I have 900 books, I have to go and fetch each of my books in each folder. The apps get really confused with the fact each book is put in a folder with the author name.
They didn't understand that some users uses Calibre to edit, and then use android apps to read. Calibre forces me to organize my books in a way that is not comfortable. I don't like Calibre, because of the way it manages the folder. I didn't speak to them, but I read on the forum, they don't care if users ask for an improvement of the not so good thing, they claim their ways are the best possible. Yes, I noticed Calibre developper are rude morons. L A Z Y!įor now, I'll just tolerate renaming a book, exit the part failed metadata edit, re-edit the metadata of the new index name, then clean out the no longer unindexed junk later. It really stinks that the help rejects fixing this broken code so that it works properly with a NAS. If you can't rename a folder because your code is moronic, like still having unclosed explicit or implicit directory locks, including directory watches or current directory handles, or doing unnecessary fail causing stuff, you can still switch to the copy and delete move approach, then leave what's left for a later clean-up, preferable marked for later deletion by name or marker file!
#CALIBRI EBOOK MANAGER FULL#
errors when the database is on a NAS in my case FreeNAS-9.3-STABLE-201503270027 with full user file permissions to a Windows 7 mapped share of a ZFS ZRAID2 dataset with windows permissions and filesystem support. Another 'feature' of Calibre which is obviously caused by some pathetic bug in the Calibre python file handling code is trying to rename books and getting nonsense permission and lock etc.
0 kommentar(er)
