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

MattP

Staff
  • Posts

    4,485
  • Joined

  • Last visited

Posts posted by MattP

  1. Status: Beta

    Purpose: Features, Improvements, Fixes

    Requirements: Purchased Affinity Designer

    Mac App Store: Not Submitted

    Download: Download

    Auto-update: Not available

     

    Hello,

    We are pleased to announce the immediate availability of the first beta of Affinity Designer 1.8.2 for macOS.

    If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.

    This beta is an incremental update to the 1.8.1 version recently released to all customers (though it installs parallel to the release). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.

    Many thanks!

    Matt

     

    Changes This Build

    - Fixes for many expand stroke and boolean geometry problems.
    - Improvements to customisable shortcuts UI.
    - Added ability to preview fonts on black or white background.
    - New document panel - terminology and UI tweaks.
    - New document panel - saves settings between uses.
    - Reinstated double click functionality on zoom, view tools.
    - Improved responsiveness when editing large blocks of text.
    - Fixed blurred toolbar buttons on non-retina displays.
    - Fixed mask bugs when resizing documents.

     

    To be notified about all future Mac beta updates, please follow this beta notification thread 

    To be notified when this update comes out of beta and is fully released to all Affinity Designer customers, please follow this release notification thread

     

  2. Incidentally, we made a DMG file that you can run and follow the instructions to automatically patch the app for you... https://affinity-beta.s3.us-east-1.amazonaws.com/download/PresetsFix.dmg

    It seems there was a 'hiccup' on our build server and it has destroyed one file on the Mac App Store build, so we're building and deploying as soon as Apple can pass it through their store. I'm really sorry for the inconvenience :(

    Thanks for your patience,

    Matt

  3. Incidentally, we made a DMG file that you can run and follow the instructions to automatically patch the app for you... https://affinity-beta.s3.us-east-1.amazonaws.com/download/PresetsFix.dmg

    It seems there was a 'hiccup' on our build server and it has destroyed one file on the Mac App Store build, so we're building and deploying as soon as Apple can pass it through their store. I'm really sorry for the inconvenience :(

    Thanks for your patience,

    Matt

  4. Hi everyone! As you suspected, this is the reason why 'recents' has temporarily disappeared from the 'New Document' dialog... 'New' document that contains a 'Recent' section implies opening that document as a new document, but that isn't what was happening... We'll talk it through and try to make it more clear what to expect and make that happen in the future :)

    Thanks!

    Matt

  5. This is not a problem with snapping. The objects are precisely aligned. The artefacts you can see have discussed many times before and are actually visible (to a greater or lesser extent) in all vector software (if you know how to provoke the problem) unless the renderer uses a different scanline rasteriser. Is this causing you an actual productivity problem? Usually there are many simple ways to work around the issue :) Let us know a bit more about how this is affecting you and we can try to help...

  6. Thank you! I'll take a look! (it's not the 'expand stroke' function itself that's causing the issue, it's the boolean operation 'add' that I run on the results to remove overlaps that's causing the problem - I need to fix this though, so hang in there and I'll take a look!) :) 

     

    Edited to say: I've just tried this in my latest beta build (I've not released it yet, but it will be 1.8.0.3) and it succeeds - but I still maintain there's a problem with the Boolean operations that causes some issues and I'll try to fix that :) 

  7. 1 hour ago, Oval said:

    better wait for the final version than use workarounds after all the years

    I agree :)

     

    The reason that the arrowhead works suddenly if it's rotated is due to an error with the arrowhead that I'm looking into - it has nothing to do with the expand stroke function itself :)

     

    Interestingly, I took your curve and tried the bit that has a problem with the expansion in Illustrator - it also shows problems. For example, here's the segment of your curve that causes our problem, zoomed in in Illustrator, before and after expand stroke... I think I've fixed ours now and I'm just testing the solution and making it sure it hasn't had any side-effects...

    Screenshot 2020-01-13 at 20.42.22.png

  8. @Mark Oehlschlager the start/end nodes are the most likely of all to have issues due to the fact that a freehand pencil/brush tool has lots of noise at the start/end. I suspect @retrograde used a Pen tool to create the source curves?

    Using your pencil/brush freehand approach, if you cleaned up the start/end nodes and then hit expand stroke, you'd probably find the results make a lot more sense. I'm just trying to say that the result of the Expand Stroke is correct, but the input given to it (from using the Wacom) is noisy, so you get noisy data out at the end, if that makes sense?

    Yes, I do wonder if the 'tolerance' of the fit could be a user-adjustable parameter... :) 

    Matt

×
×
  • 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.