Jump to content

relayer35

Members
  • Content count

    5
  • Joined

  • Last visited

  1. relayer35

    The file could not be opened because permission was denied.

    I cut down to 139 fonts, still having the problem. And no, I get that message regardless of if I open a file from the local hard drive or a network drive. I’m usually opening the files from my local drive.
  2. relayer35

    The file could not be opened because permission was denied.

    How many fonts do I have to trim down? Looks like there is 245 on my machine now.
  3. relayer35

    The file could not be opened because permission was denied.

    Why on earth should the number of fonts affect an image app, and why should it give a permission error? I shouldn't have to delete fonts in order to open an image file. (FWIW, I didn't go out of my way to install fonts, they either came with the OS or were installed by other programs). This is the only program I have that has this issue,
  4. relayer35

    The file could not be opened because permission was denied.

    I've had the problem on both High Sierra and Mojave
  5. relayer35

    The file could not be opened because permission was denied.

    I am having the same issue. It will open and save files for first few times, but after working on a number of files I get the "Failed to Open File" message box saying that "The file could not be opened because permission was denied". If I close Affinity Pro, and re-open it the file opens correctly. I haven't been able to figure out any sort of pattern as to how many files I can work on before getting the message, or how long the program is open. I tried the steps outlined here for cleaning the font cache but it did not solve the problem. I don't know why fonts would have anything to do this anyway. This seems like a problem that should be fixed by the developer.
×