Page 1 of 1

Why no support for long media file names?

Posted: 06 Jan 2023 02:22
by strathglass
Or more specifically, why the limit on overall file path length?
Does FH7 not support long paths?
I already have "Enable Win32 long paths" turned on for my Win 10 Pro PC.

And yet FH7 presents a broken link for a bunch of media with long filenames (including path).

I tried to fix one of these broken links manually by clicking on the file link in the media dialog, and then navigating to and selecting the right file.
Well, the photo now shows, but with the wrong file name!
Or at least, it is only using the Windows 8.3 short filename!!

Re: Why no support for long media file names?

Posted: 06 Jan 2023 08:34
by Mark1834
Correct - like many old 32-bit apps, FH does not support Windows 10/11 long file paths. I suggest you raise a ticket with CP to get their comments.

Re: Why no support for long media file names?

Posted: 06 Jan 2023 10:41
by Gowermick
Is it to make FH backwards compatible for FH users on old windows?

Re: Why no support for long media file names?

Posted: 06 Jan 2023 13:58
by Mark1834
I don’t think it’s that, as apps still run in Win 7/8 (but without long file name support of course).

A bigger reason could be that even if FH were upgraded, plugins still wouldn’t support it, as the core Lua libraries are off the shelf rather than bespoke to FH, and they probably don’t want to deal with that complexity for a niche application.

Re: Why no support for long media file names?

Posted: 07 Jan 2023 00:00
by strathglass
Thanks Mark. Maybe one day it will get updated.
In the meantime it is manageable but a bit annoying because I do have to do some workarounds.