Hi Mike,
argh...is this limitation still there?
That dates back to the days when all we had was FAT and FAT32.
Haven't programmed for the win32 API in ages...thought that was gone long ago...but thinking about it it makes sense since there are useability issues in Windows Explorer with files in deep directory structures (where paths get very long).
Coming back to your sugestion to work around this:
In my current very special usecase I came across this it would help but I don't think it would be a good idea to implement such a hack as it most certainly would screw many other cases. There is no virtue in knowingly imlementing bad design to circumvent shortcomings elsewhere unless absolutely required.
I can work around this problem by being careful when chosing files in the first place. Now knowing the technical reason for this I will try to shorten the paths where I store my pdfs.
Kind regards,
Michael
argh...is this limitation still there?
That dates back to the days when all we had was FAT and FAT32.
Haven't programmed for the win32 API in ages...thought that was gone long ago...but thinking about it it makes sense since there are useability issues in Windows Explorer with files in deep directory structures (where paths get very long).
Coming back to your sugestion to work around this:
In my current very special usecase I came across this it would help but I don't think it would be a good idea to implement such a hack as it most certainly would screw many other cases. There is no virtue in knowingly imlementing bad design to circumvent shortcomings elsewhere unless absolutely required.
I can work around this problem by being careful when chosing files in the first place. Now knowing the technical reason for this I will try to shorten the paths where I store my pdfs.
Kind regards,
Michael