Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'afb-6077'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Staff and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.5 Beta New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. Affinity all products 1.9.3 - i see this in publisher Mac, but it is certainly all the same problems on Windows and the all apps. I said this 3 years ago: Affinitys swatches are built wrong. Anyone using a swatch does this is in the assumption that elements it applies to stay connected to the swatch. Therefore changing the swatch all elements change with it. Would a user not want tis connection, he would simply define independent colors on the color mixer instead of defining a swatch. The connection is the whole reason why swatches exist, otherwise why bother defining one? But in affinity, if you want elements connected to a swatch this way, you have to learn using Global swatches and know how to do it and always be very careful in applying. The slightest error and you end up with elements that do not change when changing the swatch. Furthermore, despite you then have an element with a connected gobal swatch - when copy paste to another document, the swatch does not come with it. There is again another type of swatch for that - why do things simple, when you can do it complicated so everyone has to read a book or flood the forum before being able to use affinity products - seems to be the motto at Serif. And there are so many more subtle wrong implementation in Affinitys GUI that make their usage so frustrating and errors happening so frequently. One of many examples: You define a color for a text style, say you use a specific swatch and highlight it. You close the style setting. If you later check, open the edit window of that style again and check its color, the color mixer comes up, you have to change over to the swatch list and even then you still do not know what color is set because no swatch is shown highlighted. And dont get me started on the handling of paths and path points, the missing of a fundamental distort tool in Designer - all that defies any logic too. As an interface designer and founder of the FreeFreeHand movement, I gave such input to Affinity already three years ago FOR FREE and they still don't get it. Do not understand me wrong. I am using Affinity products every day and I am glad they are around. But I would have much more confidence in them, if those fundamental functions would work correctly, instead of me having to work around them all the time.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.