Jump to content

Bryan Rieger

Members
  • Posts

    428
  • Joined

Contact Methods

  • Website URL
    https://bryanrieger.com
  • Twitter
    bryanrieger

Profile Information

  • Location
    Montréal, Canada 🇨🇦

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @NathanC if you use View > View Mode > Wireframe > X-ray any pixel elements will appear dimmed/semi transparent when the document colour space is set to RGB. However when using CMYK colour space pixel elements are drawn only showing their bounding boxes, which is the same as switching to View > View Mode > Wireframe > Outline. I'd consider this a bug, and would expect the same behaviour regardless of colour space.
  2. Unfortunately the expand stroke issues in Designer go back over a decade - right to the very beginning, and the first version of Affinity Designer.
  3. I don't think they're finished putting all of the bugs in it yet.
  4. 2.0 was touted as a BIG redesign and UX/UI improvement of the 1.0 apps. Unfortunately for many the 2.0 UX/UI is considered far worse than 1.0 one (which still had it’s own issues).
  5. Or it could be that the unclear terminology used is the direct result of ambiguity present in the application. The icon names in question; hamburger and meatballs, are a common, lighthearted reference to icons that have become ‘standard’, but don’t really communicate what they do (menus), or what they contain. While I’m familiar with the Apple and Affinity documentation, it doesn’t change the fact that I still relate to both of these icons by what I actually see. Expecting users to RTFM to be able to refer to an icon using the specific terms Affinity intended is a big ask. Perhaps, it should be taken as a sign that their 2.0 UI/UX redesign is still confusing to some users. On whether it’s a bug or not was my failed attempt at sarcasm as there are so many unaddressed, long-standing issues that it’s unclear if Serif actually views these ‘issues’ as bugs or features.
  6. Thanks @walt, but I'll just stick with 'hamburger' and 'meatballs' as that's how they present (and I relate to them) in the UI.
  7. Since the Canva acquisition it feels like they've even stopped trying to compete with themselves.
  8. I have absolutely no idea what's considered a feature or a bug with any of the Affinity apps anymore. I'll leave it to whatever Affinity/Canva/Serif staff are still around to place this post where it makes sense to them, and hopefully it gets fixed, implemented, or whatever…
  9. When using the '…' menu (I have absolutely no idea what it supposed to be called) on the iPad it usually disappears after performing an operation; copy, cut, paste, etc - but it remains visible after 'Paste Inside' which forces me to always have to close it myself after performing a 'Paste Inside' operation (which I use A LOT).
  10. Every time I have to move something forward or backward on the iPad I'm always caught up that 'Move to Back' is at the top, while 'Move to Front' is at the bottom - the same order as the desktop apps. This order might work on desktop, but it's counterintuitive on the iPad. Please consider reversing the order with 'Move to Front' at the top of the list and 'Move to Back' at the bottom, ie: Move to Front Move Forward One Move Back One Move to Back Also, is the '…One' really necessary? Can it be set to Two or Three? If not, it doesn't really communicate anything useful.
  11. I don’t have much to add beyond what’s already been said (many times), but my biggest disappointment is the radio silence we’ve had from Serif (and Canva) management since the acquisition. 2.5 was an utterly botched release so that Ash could get up on stage and take part in High School Musical - Canva Edition. I’m glad Serif are taking their time with 2.6, but that still doesn’t change the fact that in the meantime, trust in Serif and Canva for many folks continues to erode rapidly. I don’t participate here much anymore (the website takes far too long to load after the recent forum update), and I’m tired of hearing that issues are logged with developers- often for years on end, without resolution.
  12. I'm trying to use the Google font Playpen Sans in the Affinity 2.5.5 apps and I'm running into text layout issues when it comes to contextual alternates. The breaks and spacing are all wrong as demonstrated in the following video. Disabling contextual alternates does render the font correctly, but without any support for alternates (which isn't ideal with handwriting fonts). FWIW the font works correctly in Pages, Safari, Chrome, Canva, Illustrator, etc. PlaypenSans.mp4
  13. Because the guy doing your print run will forever curse your name, wonder why you didn't just include a slug, and likely charge you double.
  14. Just to follow up on my font theory (above). In looking at the original 31.4 mb PDF in Acrobat Pro, it appears that all of the fonts have indeed been subsetted in the original export. I then exported another version from Acrobat Pro using the File -> Compress a PDF option and the resulting file was just under 4MB. Not sure what's going on here, but there's definitely some inconstencies in Publisher's output.
  15. Just adding yet another +1 to this? I can't believe that it's still not a feature in Publisher. 🤦‍♂️ Back to InDesign for this project.
×
×
  • 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.