Jump to content

jeffreydevey

Members
 View Profile  See their activity

  • Content count

    22

  • Joined

  • Last visited

Community Reputation

1 Neutral

See reputation activity

About jeffreydevey

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  1. jeffreydevey
    I've set aside Affinity Designer for quite a while (roughly four-and-a-half years, according to this thread) due to frustrations with the way it handles paths and nodes (one such frustration shown above). I recently came back to give it another try to see if the functionality had been improved, but the behaviors of the pen tool and boolean operations haven't changed. I feel like if a few of these functionalities were addressed and improved, Affinity Designer would be an app I could use in my day-to-day workflow, and I could happily recommend it to my peers in the design community, any of whom would happily switch from Adobe if there were a viable alternative. Sadly, I'm losing faith that this will ever happen. I admire the hard work the Affinity team has put into developing the app (which I'm sure has been no easy task), but, as it stands, I can't recommend the software to anyone but hobbyists.
  2.    carl123 reacted to a post in a topic: Cannot Save: "Save failed because you do not have permission to create a file in that location."
  3. jeffreydevey
    Another update. Shortly after setting my Mac up again after the reinstall, I tried opening a file with Affinity Photo and my issues were back. Affinity Photo refused to open any files. After a bit of research, I found a link to another part of this forum and discovered these issues were caused by too many files in use by sandboxed apps, which can include fonts. I was using a third-party font manager, and decided to try uninstalling that and using Apple's built-in FontBook app instead. After doing this and restarting, Affinity Photo opened files without issue. I'm posting this here in case it helps solve anyone else's problem. Here is the link to the other thread for more info: Cannot open or save with both affinity designer and photo beta
  4. jeffreydevey
    I recently erased my HD and did a clean install of the OS on my machine. This fixed my issues. Kind of a pain, but the problem seems to be on Apple's end, not Affinity's. I was blaming Affinity until I started having similar issues with Pages, Apple's own app. Apologies to Affinity ... I'm looking forward to giving the apps another try!
  5. jeffreydevey
    Bumping because the original post is nearly a year old. Is there another solution? I've tried all of the above, and am still getting the error message in both Affinity Designer and Affinity Photo. I'm running MacOS 10.13.6, Affinity Designer 1.6.1, and Affinity Photo 1.6.7.
  6. jeffreydevey jeffreydevey changed their profile photo
  7. jeffreydevey started following Boolean operations with compound paths, Cannot Save: "Save failed because you do not have permission to create a file in that location.", Snap to nodes? and and 3 others
  8. jeffreydevey
    I'm receiving the same error message, and have tried the solutions mentioned above without success. My other programs can write files with no issue, but trying to save with both Affinity Designer and Affinity Photo produces the same error message on my machine, rendering the apps useless until I can find a solution.
  9. jeffreydevey

    Snap to nodes?

    jeffreydevey replied to bpedit's topic in Affinity on Desktop Questions (Mac and Windows)

    I'm going to second this request, as it's a fairly essential part of any workflow that involves precision.
  10. jeffreydevey
    Is there a plan to make a more efficient action to achieve this result? Simply being able to select a line segment with the node tool and hitting 'delete' would save a lot of extra clicking, especially for those of us who do this quite often.
  11. jeffreydevey

    Boolean operations with compound paths

    jeffreydevey replied to jeffreydevey's topic in (Pre 1.7) Bugs on Mac

    Hi Matt, Thanks for your reply. Sorry I didn't make the file more self-explanatory. Thanks for giving me a workaround solution I can use in the meantime, I'll give that a try. Cheers, Jeff
  12. jeffreydevey
    I'm experiencing this problem as well. I'm glad it's a known issue. My problem is I am running a 27" iMac as my secondary monitor, and a 24" Cintiq as my primary, so I can't use the disconnect method as a workaround.
  13. jeffreydevey

    Boolean operations with compound paths

    jeffreydevey replied to jeffreydevey's topic in (Pre 1.7) Bugs on Mac

    Here is an example of what I'm trying to accomplish. Note that the color has changed on the bottom version after the Subtract operation was applied, and cannot be changed using the color sliders. Compound Boolean.afdesign
  14. jeffreydevey
    After performing a boolean operation on a compound object, I am having issues changing the color of the resulting object. It seems like the program is creating an extra copy of the compound object when performing the operation.
  15. jeffreydevey
    +1
  16. jeffreydevey
    Currently both ends of the Wacom pen act as the same tool while drawing. Also, when switching between the brush and eraser tools, it would be nice if the size of each respective tool would remain independent from the other. Changing the size of the eraser shouldn't affect the size of the brush, and vice-versa.
  17. jeffreydevey
    Another instance this would be useful:
  18. jeffreydevey

    Option key when closing path

    jeffreydevey replied to jeffreydevey's topic in Older Feedback & Suggestion Posts

    Also want to add that the Affinity team has done a brilliant job, and I enjoy working with the program so far. :)
×