Hi Kovid and thank you for your quick reply.
Your installer blocks the installation when the root path is located too deeply inside the folder structure to avoid a very particular (rare) case.
In fact a real problem arises only in case the user:
- uses the built-in library
- loads a book from an author with a really long name and with a title with an equally long name.
So if I well understand you are working in an hyper-conservative way.
I'm wondering:
- Can't you check and eventually block the use of the built in library only
at run time when you check that the root path is too long according with your rules?
Consider that a portable application, differently than an installed one, could be freely moved from the initial folder. So an initial valid root could become invalid, always according to your rules, but perfectly valid for Windows after a moving and you don't notice at all.
Well I'm here only because I'm a big fan or your program and I would like to include it in a great suite of program. No criticisms towards your work that is the most valuable worldwide in its category
