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

matt.baker

Members
  • Posts

    205
  • Joined

  • Last visited

Reputation Activity

  1. Like
    matt.baker got a reaction from Aammppaa in Nudge distance based on document units - not fixed units   
    Re-adding this as it's still not implemented and seems the most logical approach.
    I imagine the majority of users wouldn't want to nudge by pixels when their document is set to millimetres, or nudge by mm when their document is in inches.
    At the moment the nudge distance is absolute/fixed, why not give an option to make it relative to the document units.
    Existing:

     
    Suggested:

     
     
  2. Thanks
    matt.baker got a reaction from MmmMaarten in PERMANENTLY Reset bounding box   
    @Chris BIs there any more news on this, please?
    Even the boolean workarounds don't work for me. Add and intersect just keep the original rotated bounding box. This means the create artboard from selection is far too big as it's using the bounding box diagonals.
     
    Maybe it could be an option called flatten transforms.
  3. Like
    matt.baker got a reaction from ronnyb in PERMANENTLY Reset bounding box   
    @Chris BIs there any more news on this, please?
    Even the boolean workarounds don't work for me. Add and intersect just keep the original rotated bounding box. This means the create artboard from selection is far too big as it's using the bounding box diagonals.
     
    Maybe it could be an option called flatten transforms.
  4. Like
    matt.baker reacted to Chris B in PERMANENTLY Reset bounding box   
    I agree 100% so I've updated the request as it hadn't been nudged for a while - thanks!
  5. Like
    matt.baker reacted to ronnyb in PERMANENTLY Reset bounding box   
    PLEASE enable a PERMANENT way to reset an object’s bounding box without workarounds! 

    I posted about this in 2015 and it’s still an unresolved issue, with users asking about this in the OP. Is there anyway to make this permanent, ie, baked into the object? it’s really a hindrance to constantly work around BASIC functionality… PLEASE!
    https://forum.affinity.serif.com/index.php?/forum/138-21-new-features-and-improvements/
    Thanks for your consideration !
  6. Like
    matt.baker reacted to Ben in Reset Bounding Box   
    Coming soon...
  7. Like
    matt.baker reacted to Austiemo in Gundam (Wing) Collection   
    The collection of fanart I created in Affinity Designer over the years of characters from Mobile Suit Gundam Wing.
    Instagram: Austiemo
    Webstie: Austiemo.com/portfolio
    Facebook: Austiemo












  8. Like
    matt.baker reacted to Mark H. in Affinity Designer SVG export with reliable scale   
    I'm just going to reiterate a previous answer, and clarify what the problem is. 
    The problem is that when you export to SVG, the default settings don't include the original size of the artwork in the exported file. Instead, it sets the width and height to "100%". It does this, I think, to make viewing it in a browser a little better, but it doesn't play well with output hardware like laser or vinyl cutters.
    One workaround mentioned was to uncheck the "set viewbox" option. Unfortunately, this only makes it export the width and height in pixels, which is often device-dependent, so it doesn't always fix the issue either.
    The best option is to edit the file in a text editor after export. Find the spot where the width and height are set at the top of the document, and change the values to the actual values for the size of the document, such as:
    width="8.5in" height="11in" You can use in for inches, cm for centimeters, etc. Note that this will completely fix the problem, so it's a workaround, not a hack.
    Perhaps, Affinity, you could work this in as an option for SVG export? It honestly seems like it should be the default, but I'd settle for a checkbox to export at the chosen size.
  9. Like
    matt.baker reacted to jango_fx in Affinity Designer SVG export with reliable scale   
    in v2 still the same issue...

    workaround for now: export with 2540 DPI. seems to scale at least halfway reliable by 100. you still get minor rounding issues due to floating point accuracy, of course... but to a 0.1mm precision it seems fine
  10. Like
    matt.baker reacted to Mindflow in Preserve document units in SVG export   
    When drawing elements to be cut on a laser cutter, setting up a document in mm is very helpful. Unfortunately, the common interchange file format for this kind of device is SVG. While the file format supports measurements in defined units, Designer converts to pixels during the export, which means that after import, the dimensions have to be recalculated.
    Therefore, it would be great to have the option to preserve the units from the document during export, such that a 50x150mm rectangle is exported just as such.
     
  11. Like
    matt.baker got a reaction from keiichi77 in Isolation / group edit mode (similar to Illustrator)   
    I would like a mode where you can open a group or other container and edit these in isolation where all mouse and keyboard events stay within the group. For example Ctrl + A selects everything in the isolated container and not the other parts of the document, clicking and dragging (for selecting multiple objects) outside of the container doesn't cancel the container edit mode etc.
    When in this mode the other objects in the artboard/document should become more translucent/faded to indicate they are not being edited.
    The following video shows entering the isolation mode by double clicking in Illustrator and this is what I would like:
    https://helpx.adobe.com/uk/illustrator/using/selecting-objects.html
    https://www.webucator.com/how-to/how-use-isolation-mode-adobe-illustrator.cfm
  12. Like
    matt.baker reacted to Ash in Affinity V2, updates, pricing and no subscription [repost]   
    Hi All,
    Well, it’s been a pretty crazy week since the launch of V2!
    This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
    With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
    Updates to V2 moving forward
    Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
    It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
    Updates to V1 moving forward
    While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
    We will update our FAQ shortly to make that clearer for everyone.
    Offer period
    In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
    Upgrade pricing
    It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
    I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
    The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
    Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
    However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
    We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
    A comment on no subscription
    I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
    We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
    But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
    All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
    All the best,
    Ash
    This is a duplicate post of a thread that is now locked and moved to the questions forum
  13. Like
    matt.baker got a reaction from Intuos5 in Isolation / group edit mode (similar to Illustrator)   
    I would like a mode where you can open a group or other container and edit these in isolation where all mouse and keyboard events stay within the group. For example Ctrl + A selects everything in the isolated container and not the other parts of the document, clicking and dragging (for selecting multiple objects) outside of the container doesn't cancel the container edit mode etc.
    When in this mode the other objects in the artboard/document should become more translucent/faded to indicate they are not being edited.
    The following video shows entering the isolation mode by double clicking in Illustrator and this is what I would like:
    https://helpx.adobe.com/uk/illustrator/using/selecting-objects.html
    https://www.webucator.com/how-to/how-use-isolation-mode-adobe-illustrator.cfm
  14. Like
    matt.baker got a reaction from nicolasfolliot in Collapsible studio palettes / panels (icon view)   
    Collapsible palette functionality that reduces the palettes into an icon.
    This would allow more screen real estate when working on designs.
    Clicking the palette's icon should restore that palette as a fly-out with the others remaining collapsed.
     
    Similar implementation to Adobe Photoshop / Illustrator (shown below).

     
    Also mentioned here: https://forum.affinity.serif.com/index.php?/topic/16282-cvollapsible-palettes-export-preview-actions-glyphs/?p=73830

  15. Like
    matt.baker reacted to MEB in Boolean add fills hole   
    Hi @matt.baker
    Go to menu Layer > Fill Mode > Alternate to fix it after the add operation.
    Alternatively change the direction of one of the objects: you can do it with the Node Tool, Reverse Curves button (the last icon pin the Action section).
  16. Like
    matt.baker reacted to Sean P in Inconsistent stroke mitres when zooming   
    Thanks Matt! This is something we're aware of and I have just bumped the issue with development again.
  17. Like
    matt.baker reacted to Joachim_L in Expand stroke (again)   
    You have to admit, that the height of 3,9 px is not much. AD seems to have problems with expanding such small elements. As often you can workaround: Check scale with object at the Stroke panel, scale the element by e.g. 400%, expand stroke and scale by 25%.
  18. Like
    matt.baker reacted to Sean P in Expand stroke (again)   
    Thanks Matt! I'll get this passed over, as Joachim_L has suggested scaling it up does work.  
  19. Like
    matt.baker reacted to Chris B in Opening a DNG file - unable to quit (normally)   
    There are indeed a few DNG issues logged and unresolved - I did check this yesterday but nothing seemed similar. Also, because others were not able to reproduce, it would normally be assumed drivers are at fault.
  20. Haha
    matt.baker reacted to Chris B in Opening a DNG file - unable to quit (normally)   
    Fantastic. I just tried on my Surface that hasn't been updated for about a year 😬 and got a similar result. However it did eventually open after about... I lost count/got distracted  

  21. Thanks
    matt.baker got a reaction from Chris B in Opening a DNG file - unable to quit (normally)   
    @Chris B forcing an update of the display drivers on my Surface Pro 5 from the Microsoft 09/2020 Surface specific (latest available) to Intel 02/2021 ones has fixed the problem. My comment still stands about the UX though with a progress bar / operation cancellation.
  22. Like
    matt.baker got a reaction from Chris B in Opening a DNG file - unable to quit (normally)   
    Hi Chris
    The attached DNG file has the same issue. Perhaps it's incorrectly formatted. It's from an Akaso action camera.
    Are there any plans to improve the user experience when opening a DNG file, such as adding a progress bar and the ability to cancel the operation, similar to Designer?

    SINR0018.DNG
  23. Thanks
    matt.baker got a reaction from Chris B in Opening a DNG file - unable to quit (normally)   
    @Joachim_L Perhaps it's a regression then? Does it work with the latest beta 1.9.4.1065?
    This is what happens on mine:

    lw7Z19uvoa.mp4

  24. Like
    matt.baker reacted to Sean P in Cursor cross-hair difficult to see on dark grey   
    Hi matt.baker,

    I do see this on my machine here. It is something we have open with development to be looked into. I'll get your details passed over and get it updated.

    Thanks for letting us know.
  25. Like
    matt.baker got a reaction from midvok in Node tool: Snap to segment / line midpoint   
    It would be useful if when hovering over line segments, it would allow snapping to the midpoint of the segment.
×
×
  • 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.