chessboard

Maybe so. But it seems to me that there is more going on than just ignoring nodes. In the DWGs there are straight lines between all nodes. If Affinity just ignored the nodes, then the result would just be an extreme abstraction with only straight lines as well, and the shape would be far from the shape of the DWGs. As Ash has shown, the result is Bézier curves with smooth nodes and recalculated tangents. So there must be an algorithm to recreate the curve or shape. Either way, I can't see what the problem is with introducing a function to simplify the path. Every vector software I know has this, even Photoline can do this. I am tired of waiting for this function for almost ten years now.

Well, now that this exists - wouldn't that also be a nice algorithm to simplify ANY path or shape, no matter if it's imported or drawn in the Affinity-Apps directly? Or to put it more clearly, can we now have a "Simplify path" command?

Hoped for a solution in 2.4.2, but this bug still exists. This makes layer states obsolet for my current project, though I could really benefit from it.

I've been in the graphics business since the early 90s and have seen a few of these takeovers. Experience teaches us not to trust the acquiring company, because these companies are primarily interested in the customer base of the acquired company and the money of its users, not in making the products better. And the announcements about the pricing model are just as similar as the statements made by the CEOs of the acquired companies. "A great future in a great partnership with the new partner. Great things are already shining on the horizon." And so on, and so on. All heard umpteen times before. And the real development has been seen umpteen times. And the contributions to the discussion are the same every time, including the call to have a little faith in the companies. It's all been done before.

Pigeon not only talks about the missing features, but also about the bugs. I came here for the same reason (the bugs), and was glad to see someone talking about them, so I think his post is valid. Therefore my +1 for reporting the bugs. Incidentally, it is not always easy to find an existing post on a topic because users often use completely different terms in the title of their topic than you would search for yourself.

Thanks Walt. That's it. I was wondering why I couldn't find a post about such an obvious bug. However, I searched the forum for "Styles" and "Appearance" in connection with States. OK. This thread may be deleted then.

When switching states with "Effects changes" turned on (which is the default state), this destorys the object styles (appearance) of all objects in the document (on all artboards and all spreads). This can be reproduced in all Affintiy apps. Here the state before switching to state "only 1 and 3": Here after switching to the new state. In the Layer studio you can see that all styles have been removed. Just stroke and fill attributes are left.

@Pšenda Yes, this is what I thought of.

I would like to bring this up again. Especially on Hires-Screens the indentation is much to small. A larger indent would be much better for better readability. An option to set the width of the indent would be best. And more colours could help to here. For example, according to the selected layer the vertical bars could also be colored.

Me: ChatGPT: You can get any answer out of ChatGPT if you're asking for it. As is says at point 3: "I don’t have personal experiences or subjective consciousness."

@CM0 I really doubt that this would work. But we will see. Would be nice if you could give some links to see how they did this.

I assume that chatGPT generates Blender scripts quite well because there are many references on the web that chatgpt has "learned" from, due to the open source nature of Blender and therefore a large number of users who know how to script and share their scripts on the web. Similar knowledge cannot be expected for affintiy scripts, as chatGPT does not learn to script. It does not "know" anything about scripting logic and scripting languages, nor does it understand how to read API documentation and combine this information with knowledge of the rules of a particular scripting language. It simply can't think. Instead, it simply collects scripts that others with knowledge of the scripting language have already written and can combine them into new scripts. This works all the better the more often the tasks set have already been solved and published on the web. If you ask chatGPT to create a script for a very specific and unique purpose, it is more likely to fail. Scripting in Affinity will be so new that chatGPT will not immediately find enough scripting input. If scripting in Affinity becomes popular, the later versions of chatGPT will probably also be able to generate scripts for the Affinty applications. It is not a question of which scripting language is used. There just needs to be enough sample material available.

Did you read the line: Both Jon and Tim are part of the scripting development team, not the publisher development team. They develop the scripting feature for all three applications: Designer, Photo and Publisher. I find it quite understandable that they are specialists in their field and not for photographic, design, illustration and publishing software issues.

It's a bit like locking the door with locks and chains and leaving the window next to it right open. Now you can't get into the house throught the door anymore - never! The window, ...um, well... 🙃

As far as I can see, there is a "show bleed" option in Designer in the View menu. Curiously it's missing in Photo. So no way to work in the bleed area in Photo, what is really annoying. Thus a +1 from me for this bug.