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

Everything posted by MattP

  1. @VectorVonDoom - I'm building a new 1.8.3 Beta at the moment - let me know if fixes your issues when I release it! (I'm assuming it'll be ready tomorrow) Interestingly, the iPad version has always worked in the way you're describing, so hopefully adding this to the desktop product shouldn't produce any unexpected hiccups (hopefully!)
  2. That's awesome! But... tell me more about the layers panel.... (contacting you via direct message so we can chat...)
  3. It does make sense internally - I can try to sort this out, but it may take a couple of hours... sorry about this in the meantime!
  4. Just to add to this, I've found the cause of the problem and have resolved it for the next build. Anything from build 1.8.2.4 and onwards should work fine. Sorry about the issue in the meantime... Matt
  5. Is this still an issue for you in the current Beta version? It contains a fix for this issue, so hopefully should be working? Thanks! Matt
  6. Yes, just grab the Beta and carry on as before, or simply use a different preset type and you shouldn't have the issue at all
  7. Hi Sean (and interested parties!) I'm guessing that it is simply because the object had a line weight, had 'scale with object' set on the stroke, then was transformed to flip it in at least one axis - the resulting line now thinks it has an inverted line weight? I've fixed the code to actually work correctly! Many thanks everyone, Matt
  8. Hi @BPf, There is a known bug which shows itself as a failure to save any new document that started from the 'Architectural' presets type. Just choose *any* other type of document for now... The Beta already fixes this and the official release of 1.8.2 is not far away at all. I'm sorry you're experiencing this in the meantime Thanks, Matt
  9. Hi @martdupuis, Sorry you've encountered problems - your document works and exports correctly in the Beta version of 1.8.2 and this will hopefully be deployed as the release version very soon. I suspect that (from looking at your document) the problem was probably due to a failure to expand one of the strokes in your document due to an error on my part, sorry In the meantime I can only offer my apologies, but at least a solution is on the immediate horizon. Here is an SVG export of your file from the current Beta, just to show that it works! Thanks again, Matt pivoine.svg
  10. Hi, this is currently a bug and will be fixed in the next update
  11. Hi @amyas - if you take a look at the Beta mentioned above, you can see that it is recommended to be used instead of the official release version as it contains nothing that would cause an incompatibility with files and just includes improved functionality and bug fixes. This version will very shortly be released at 1.8.2 so it should not pose any issues
  12. Hi @dcarvalho84 - sorry you're having this problem Would you mind sending me the files so I can look at it? Anything you send will be used just to fix the bug, not shared at all and deleted immediately afterwards Thank you!
  13. Hi Kevin! Thanks for the feedback on this - I really do appreciate people thoroughly testing things I do want to warn you though that I still haven't looked at the Divide operation - it gets better as a consequence of the other operations working better, but it is implemented in a sub-optimal way, so until I can give it a few days of attention then I don't expect it to be bug-free, I'm afraid... I'll definitely look at it soon, but unless I specifically mention it in a bug release then it's safe to assume I haven't invested the time and attention it requires yet... Thanks again! Matt
  14. Right, I've just found and fixed that bug, hopefully I can get a beta built on Monday and distribute that on the forum Thanks for being patient while we work through these problems! Sorry it has impacted you in the meantime... Matt
  15. 8.5 x 11 is a standard Letter page size, so it's unlikely you started from the Architectural category, so I really doubt that's where your problem came from...
  16. Next thing is: If you navigate to your desktop and then look in the 'JMT LLC' folder, do you still have a file called 'jmtllc.afdesign'? If so, is it 0 bytes, or does it have a size?
  17. Thanks Ricky - so, first thing's first... Try this: Go to the menu and find 'View' -> 'Studio' and click 'Snapshots' Now go to the Snapshots studio and click 'Add Snapshot' (2nd icon from the top left of that panel) Now select that Snapshot and click 'New document from snapshot' (the top right button in that panel) Does it let you save the document now?
  18. Hi @zimmt - sorry you've had to wait for a reply Yes, it really does look like it has been broken (I'm guessing by a Publisher change as there is new UI there for 'Page Box' area) so I'll look into it and see why that's not working... Sorry again, Matt
  19. Hi @Ricky James - do you possibly have the original of that file somehow so that we could get a copy of it and look into this? I've seen this problem mentioned in the last 24 hours by someone else but their file had been lost We have found a problem with documents created from the 'Architectural' document presets that would show itself in the same way as this, but it looks like you had probably been working on this file (perhaps opening it and working on it, then going to save?) so I'm guessing yours must be a different issue? Any information you can offer about what you'd recently done might help too? I'm really sorry about this - but thanks for your help! Matt
  20. Hi GokhanEser I think that markw was just trying to help Yes, the issues that you've posted about are still there and will be looked into - I can only apologise that you're having these problems at the moment and we'll try to get them resolved as quickly as possible. All the issues are nicely documented in your videos, thank you - and yes we've already got these in the bug database and I'm looking at them with the rest of the team. Thanks again Matt
  21. Try the latest Beta version - hopefully the issue has been fixed now
  22. 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 Affinity Designer Beta 1.8.2.1 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 - Fix for PDF export issues relating to missing straight line segments. - Allow PSD smart object import in Designer. - Further expand stroke and boolean geometry fixes. - Fix some symbol instability problems.. - Fix for some compound objects not allowing documents to be opened in 1.8. Changes Since 1.8.1 - 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
  23. I think maybe I should be a little less vague about some of the fix details, and then everyone would know that if I hadn't explicitly mentioned the thing they were thinking of, then it hasn't been fixed?
×
×
  • 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.