Jump to content

smth

Members
  • Content count

    31
  • Joined

  • Last visited

About smth

  • Rank
    Member

Recent Profile Visitors

90 profile views
  1. smth

    Failed to save document

    No, none of that. I wouldn't have posted here if I thought it was an OS issue. The error seems to be caused by something in the file. If all the layers are deleted it saves fine. Similarly "new file from clipboard" doesn't work either. I didn't get as far as pinpointing the problematic layer.
  2. tl;dr - I would like some reassurance that fixing bugs / improving performance of existing features is a priority. I just want to say this, because it's in the back of my mind, every time I contemplate using Affinity Designer for a new project. First off, I have/had high hopes for Affinity Designer, its ambition and feature set make it a really powerful and versatile design tool. To be frank, it feels like a potential Illustrator replacement, which is also geared towards layout. I think for a lot of us, that goes a long way towards the dream of cancelling our Adobe contracts (which I think is why everyone is desperate for the final piece of the puzzle - Affinity Publisher). Having said that, I'm starting to feel like the experience of using Affinity Designer is destined to be one of compromise, or giving up and switching to a competitor's product. There are a lot of bugs and shortcomings, some bigger than others. It's great that we have this forum to discuss them, but the responses often don't go beyond "we are aware". Workarounds are welcome in the short term, but without knowing when a bug will be fixed, or having the confidence at least that it will be within a short time frame, it's difficult to invest in Affinity as a viable option for the future. To give a little context, I guess the issues I'm thinking about here are those around vector operations - the problems with booleans, and outline stroke. I don't think there's any dispute that these things don't work well currently. I'm concerned that issues like these are considered "would be nice to fix", rather than "shit, out app is fundamentally broken". If Affinity Designer is serious about being a vector drawing tool (which I think it is), then I feel like the response should be the latter. In my opinion, these convenient ways of doing complex operations are not bells and whistles, but central to why we buy sophisticated apps for doing this stuff. Beyond these well documented problems, there have also been one of two issues that I have raised, that were dismissed as (rightly or wrongly) just me not understanding the intention of a feature, or something. This is also concerning. As an outsider, I obviously have no idea what priorities Serif has, what resources, or where they are being used. I can give my impression from this perspective however, and that is that Serif is doing a great job of delivering a range of feature rich apps across multiple platforms; but not such a great job of making at least one of those apps, live up to (my) expectations. I hope this feedback is useful, and is taken in the spirit of wanting the Affinity products to succeed.
  3. smth

    Failed to save document

    I thought I'd note this, in case it comes up again. I have a Designer file which I cannot save with a different file name. I get the error "Failed to save document: /path/to/file.afdesign Save failed because the file could not be written to."
  4. smth

    Inaccurate expand stroke

    Do we have an estimate of when this bug will be fixed? Is it safe to assume it will be prior to v2 at least?
  5. OK, that makes sense; and explains the resulting document size too. Thanks. I had forgotten that AD defaults to 96dpi (seems a strange choice).
  6. Examples attached. file-web.svg file.afdesign
  7. I'm a bit confused by the different SVG export presets. When I export using "for web", then reopen in AD, I see two obvious changes, neither of which are expected: There is a 0.5px transparent border along the right and bottom edges The document size has changed (I don't see where this is configured) I'm guessing these two are related - i.e resizing to a decimal size.
  8. When using the Add / Unify tool on two curves that share an edge, the result includes a bunch of redundant nodes, along that shared edge. Would it be possible to get a cleaner result from this tool? To see what I mean: Create a document with two overlapping curves, maybe a square and a circle. Unify them, and take note of the resulting nodes Undo that, now divide them Now unify them again. You should now see the nodes I'm talking about. I feel like 4 should give the same result as 2. Failing that, is there a way to automatically remove the redundant nodes?
  9. I don't have the file in that state any more I'm afraid. Upon retrying, the process completed, but gave unexpected results - some of the curves were being excluded. I guess this might be related. (This issue seemed to be caused by paths that had somehow ended up something like the attached. Tidying them up, resolved the issue). example.afdesign
  10. Union is hanging for me right now. Progress bar has been at 100% for a few minutes. This has happened after dividing some curves, making some adjustments, then attempting to unify them again. We're probably talking about 50 curves, nothing too complex.
  11. Those both sound like good options. Thanks @Aammppaa.
  12. Yes, the workaround (that I currently use) is to replicate the shape of the group. I'm suggesting it would be nice if this could be done automagically Should definitely not be limited to any one shape, but be the result of all the shapes in the group, as if you had flattened it.
  13. Yes, sorry, I was using a pixel layer. Have amended the original post to reflect this.
  14. A few of things about applying strokes to groups: It would be nice to have this working, i.e stroke apply to resulting object, rather than each of the children. Why does applying a stroke to a group containing a pixel layer, essentially apply a fill? When attempting 2, there seems to be a performance issue (high CPU usage).
×