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

kaffeeundsalz

Members
  • Posts

    456
  • Joined

Profile Information

  • Gender
    Male
  • Location
    : Germany

Recent Profile Visitors

3,114 profile views
  1. @Return Yes, that's what I found, too. Also, "Expand Stroke" gives the result from the PDF, meaning if you have the bottom A part with stroke aligned to inside, as soon as you expand stroke, it converts to a filled letter just like in the example above. Something else that helps is rasterizing the object, but this is probably obvious and is something I don't really want to do (again for obvious reasons).
  2. The stroke being set to inside is intentional in this case because I don't want it to exceed the dimensions of the original (filled) letters. I didn't try to change the stroke alignment, so thank you for pointing me into that direction. I could somehow work around the issue then by aligning the stroke to center and scale down the object a little bit to match sizes. The question I still have is: Why does this happen? Why does the outlined S part export just fine while the outlined A part doesn't?
  3. Hi everyone, I have a design that looks like this in Affinity Designer: but exports like this as PDF (regardless of the settings, as far as I can tell): The design was created using the Art Text tool, writing the letters AS in Baskerville an then using the Knife tool to cut the letters along the horizontal line. I then changed the letter appearance of the lower part by removing the fill and applying an outline. I created the files using the latest Affinity Designer 2.5 beta (2.5.0 2449), but it also happens in the current 2.4 release version. Also, I originally spotted the export error on Affinity Publisher for iPad, so I suppose it's not limited to macOS. Anyone might be able to take a look and help me understand what's going on? You'll find the Affinity Designer and PDF files attached to this post. Thank you! as_slice_outline.afdesignas_slice_outline.pdf
  4. Don't trust that any software has this implemented correctly. Check it first.
  5. Why don't you apply the gradient to the stroke, too?
  6. The mistrust stems fromt the fact that your post made an argument in favor of Serif along with your forum account being just a day old. The hidden accusation is that you are a fake member created by Serif to counter the negative comments. Which I personally think is a fairly bold thesis.
  7. In what way is this different from the situation before? Serif as well could have encountered turbulence, letting them reshape their business model. It is perfectly legitimate for you to distrust company promises phrased this way. But I don't see what this has to do with the acquisition.
  8. If there's one thing I've come to learn from 20+ years with GIMP, it's that their release cycles are entirely unpredictable 😂 Probably not the kind of CMYK support that you're hoping for. From everything I know, true end-to-end CMYK is something the codebase of GIMP is now capable of, but will not be available straight from 3.0 onwards. That's only true for the very earliest versions, showcasing a Qt based UI for GIMP in KDE. Krita was developed from scratch soon after. What you want is full end-to-end CMYK support in GIMP. As long as that's not available, notice that CMYK support did improve significantly in GIMP over the last years. We got CMYK color proofing and even CMYK export features (so for many formats, the workflow you mentioned above is not necessary anymore). It's still a long way to go though.
  9. As of GIMP 2.99.18, that's not true anymore. Granted, it's a developer preview, but non-destructive adjustments are already fully implemented.
  10. The question is: Why would they? For any company, it would be incredible stupid to rule out anything forever.
  11. Well, we'll see how all of this turns out in the long run, especially for the users. I wish Serif all the best for being part of Canva. Let's give them a chance to prove that the well-known narrative of the evil giant swallowing up small software companies doesn't apply in this case. I am looking forward to the features that are yet to come for the 2.x versions, really hope that the planned Q&A session will shine some light on future plans and will follow the development of v3 with great interest.
  12. I'm not an offender of subscription models in general. If they are fairly priced (which I know is a highly subjective manner), I'm happy to give them a try. With Serif, I don't know. What I'd like them to be is a healthy competitor for Adobe because I think that benefits the creative market, and one-time purchases are one area where the two companies differ. That said, I'm also a happy Affinity user, so anything becoming more expensive for me would of course be disadvantegous. On the other hand, subscriptions don't necessarily mean an increase in pricing. There are countless examples where this was the case, but it's not set in stone and also depends on how the user handles updates, upgrades etc. The more important point for me is the integration thing because I don't like user interfaces that try to cross-sell other products and services. I do accept Studio Link in Affinity Publisher because I really see the benefit of that level of integration (it's a dream to use) and after all, that's why there's a universal license that lets me purchase the entire suite for a fair price in case I want it. Also, everyone who decides to buy Publisher as a standalone application can very easily customize the main tool bar and get rid of the persona buttons. The same was true for the old Welcome screen: It did advertise addons, but you could choose to turn it off and never see it again. This is how it's done: Don't constantly give users the subliminal feeling that they are missing out on something or have just bought a lite version of your software. Don't let buttons triggering addon services that I'm not subscribed to eat up precious screen real estate. Let me hide every upselling attempt quickly and effectively because I really know best what I need and don't need to get the job done. In other words: If Serif were to integrate big buttons with Canva logos on them that I can't hide, I'd be upset.
  13. The title pretty much says it all. Serif has been acquired by Cava: https://www.canva.com/newsroom/news/affinity/ Now I wonder mainly about two things: 1. Will the Affinity suite give up on its one-time purchase philosophy (given that Canva is a subscription service)? 2. Will we see integration of Canva services in the Affinity applications and if so, will users be able to hide it in case they don't need them? I know that it might be a little early for definitive answers, but since we only have the Canva press release so far and no official statement from Serif yet, I was hoping that staff might be able to comment on this.
  14. Shift+Command+K is hardly the industry standard for creating a symbol (at least to my knowledge), it's just the keyboard shortcut that Serif chose to assign to this function. Since it triggers a menu command (Layer > Create Symbol), it's configurable! Just choose whatever key combination seems appropriate to you.
×
×
  • 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.