CM0

I think the argument about the old road maps are kind of redundant at this point, yes. Serif's approach to announcing features and changes in V2 are much different from when they decided to scrap the road maps. We may no longer have a road map, but the transparency around development is a night and day difference, and for the better I would say.
The only thing I do wish they could do better is announcements done through articles like the one linked by R-C-R. It's not the first time I have read interesting announcements they've done in some article that I had to search up myself through a search engine. Their X/Twitter and YouTube accounts also have made interesting announcements which at least have been a bit easier to find. I hope they keep improving their communication channels, since I think they've been moving in a good direction as of late.

The way I see it, scripting is going to be the best solution for implementing AI features. It would open the door to a lot of new possibilities for 3rd parties to utilise the Affinity ecosystem. Still, AI features are something the devs should definitely consider adding in on their own as well, since there is going to be enough demand for it in the coming years. As of now it is not going to be a make or break deal, since there are a lot of alternatives out there that can be used over what the likes of Adobe have to offer while keeping Affinity as the main place for editing images, but it's important to have a plan for the coming future.

We can assume some level of competence in how to approach information sharing. Many companies do this just fine.
I do believe the new shorter iterations are at least a positive improvement. It allows for more input from the community before features are finalized in the release and quicker turnaround for issues to be addressed. It feels like Affinity is more in touch with the users with this approach and hopefully will continue with such process improvements.

We can assume some level of competence in how to approach information sharing. Many companies do this just fine.
I do believe the new shorter iterations are at least a positive improvement. It allows for more input from the community before features are finalized in the release and quicker turnaround for issues to be addressed. It feels like Affinity is more in touch with the users with this approach and hopefully will continue with such process improvements.

There is an entire thread on scripting with demos.
 
No we haven't
BTW, you were previously complaining about revealing too much and now complaining about too little. 

And yet they have just revealed two major items. AI ,scripting and other small details mostly to the praise of everyone. No matter what your complaint is about a company, that complaint comes with the assumption they can improve. I've worked in the tech industry for decades and have seen many decisions by executive management that later were reverted because it didn't work out as intended. Options are not simply binary choices.

Yes, their major advantage is already lost. There are already free versions. No need to switch and pay for it. MS just now added it even to MS Paint in windows 11.
If you want selections combined with generative fill, then Krita has it for free. The reason Krita has it is because they have good plugin/extensions. Which continues to be my argument for Affinity. They are already working on it. It is the best path forward in this crazy rapidly changing landscape to simply allow integration with whatever will be coming.

That is more of an argument to not include such plugin in Affinity. The video is even making the argument the plugin is better than Adobe's generative fill.
Instead, we just need the scripting/plugins API for Affinity. That is how Alpaca was made available for Photoshop and Stable diffusion for Krita etc. No company can keep up with the pace of AI development. Whatever they include will be obsolete almost by the time they ship it.

That is more of an argument to not include such plugin in Affinity. The video is even making the argument the plugin is better than Adobe's generative fill.
Instead, we just need the scripting/plugins API for Affinity. That is how Alpaca was made available for Photoshop and Stable diffusion for Krita etc. No company can keep up with the pace of AI development. Whatever they include will be obsolete almost by the time they ship it.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

I believe R C-R is referring to the following:
https://realsound.jp/tech/2023/09/post-1446012_2.html
Translated:

Look, if somebody wants to feel like he is creating something by simply writing what he wants thats fine. If you want to consider a "tool" something that does everything - I cant stop you. People have all sorts of fantasies about themselves, all sorts of delusions and I will not judge that. But also dont expect me to call you a creator when all you did is telling what you want. By this standards you would consider yourself a builder because you said a guy where you want to have a window and he did it for you. An electrician - when you said to a guy that you want to have a new lamp hanging from the ceiling and he did it for you. A plumber - because you have pointed to the sink thats clogged. And so on.
If you want to consider yourself a driver while sitting in the passenger seat thats cool with me. But please kindly dont expect me to join you in believing in that illusion. And by all means - have fun with your toy steering wheel making "brooom! brooom!" noises while somebody else is driving. Its important to have fun in life.
Now if you excuse me - I need to catch a plane.
I'm a pilot, you know. I told the person at the counter where I want to fly.

If you want to stretch it then anybody who had any idea ever technically was part of creative art. That will make literally everybody an artist even if they never actually created any art. Every commissioner, every client would suddenly become artist because he had idea - therefore took part of creative process, right?
No, he didnt.
Thinking about something and actually making it is whole different story. Anybody who have ever tried to draw something will quickly notice that bringing to life, to physical world this idea, that seemed so clear in his head is in fact very vague, missing details and his hand is not drawing at all what he had in mind. It takes many years of training (hey, its me, captain Obvious) to actually make ideas reality. If somebody commissioned a piece to an artist, or wrote a prompt - he is not creator. He commissioned it precisely because was unable to create. He can have all the philosophical excuses in the world, make all the mental gymnastics in order to convince others and himself that he also is the creator. But everybody knows reality. So theres nothing to argue really. If you have paid runner to win a race you are not partly athlete Its just absurd and quite sad to see people even bringing that silliness up. If you can do iy YOURSELF you are the creator. If you need to ask somebody/something to make it for you - you are not. Simple as that.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

Nice addition!
BTW, it would also be useful to be able to reverse the stroke path when using brushes.

It would be great to add a «scale each» checkbox

Nice additional tool.
To bad it only has context toolbar options and none on canvas like other quick shapes.
The presence of nodes suggests as such but it would only draw a new spiral.

Maybe have something like this:
 

2023-10-25 13-58-04.mp4  

Here's a list of some of the bugs which have been fixed in beta build 2.3.0.2096
Please reply in this forum only to comment on any fixes which are in this list (in particular to let us know if you notice that something we say is fixed isn't!) To report any new bugs please do that against the relevant new feature post, or if unrelated to new functionality in the Other bugs & issues forum.
(A) Bug fixes which affected all platforms 
Fields Panel - 'Created' field fails to update when using 'Save as' on documents [AF-70] PDF passwords - Allowable characters not consistent between creating and opening [AF-124] Unable to place/open password protected PDF created by Acrobat [AF-121] Changing Language of text and updating Text Style does not remove red squiggly spellcheck lines under text in a separate frame until reopening file [AF-50] Cross references - allow anchors and index marks to be filtered by name [AF-2] When a document is opened, the Index panel may show limited or no entries until Update is clicked  Edit placed pdf doesn't show any layers in the layers panel  Word footnote imports with tiny font size  DWG file stuck on loading [AF-346] Presets can't be added for just the black and white adjustment [AF-520] (B) Bug fixes which affected Desktop (Windows and macOS)
Editing placed PDF fails to save changes until source file is saved and reopened [AF-31] Opening a password protected file (Made in publisher) fails to render images  Copying a frame with an index in allows multiple indexes to be in the same document [AF-329] Unable to delete selected anchors from TOC in user file [AF-30] Running Headers Settings- Inconsistent casing on dialog settings [AF-42] It should not be possible to use 'Move Inside' to place a Symbol inside itself [AF-562] View > View Mode >Hide effects inconsistency [AF-644] Alt + Click / Alt + Shift + Click on a new brush to retain size no longer functions for Pixel tools [AF-463] User File - Select Same > Fill fails to detect other objects with the same HEX applied (possible rounding error?) [AF-527] Replacing Style Source Chapter in Book results in Book without a Style Source Chapter - app crashes when exporting/printing file [AF-223] Paragraph break point regression over V1 allows commas at the start of line [AF-38] Hyperlink control value not set when choosing a preset  Unable to launch the app without linking my app to my account - licence specific  User File: Text Wrapping issue with vector cropped embedded PDF document [AF-58] Table of contents and Index Page numbers do not update on Book Output [AF-59] Cross-references can be inserted on a Master Page but do not function as expected on Pages  Toggling scale override in the transform panel clears the move data entry preview  Clicking at the end of a line with a break character can incorrectly position the insertion point [AF-57] Exporting a file with substituted fonts to Password PDF fails to load images and text when opened [AF-19] Placed restricted PDF fails to draw when switching from passthrough to interpret  Saving a book silently fails if saving to a disconnected device  Hyperlinks to anchors in different chapters warn that the anchor is off spread  On the Edit Table Format dialog, you can't type values for the Frame or Cell Format's Fill setting  Hyperlinking to book chapters requires the anchor to be re-selected  Text doesn't re-flow when group size indirectly increased [AF-333] Password protected PDFs fail re-linking when missing resources  Previously viewed page fails after text entry  Embedded profile isn't recognised when opening a Password Protected PDF exported from Publisher beta Tooltip for Create Custom Field is incorrect after deleting Custom fields [AF-17] On the Edit Table Format dialog, tooltips are the same for table and cell insets  Packed Footnotes can appear in the wrong linked text frame [AF-834] (C) Bugs fixed which specifically affected Windows
Mouse cannot control text caret when renaming existing anchor [AF-312] Develop Lens Correction does not function on macOS Sonoma [AF-513] The Font search box can expand to fill the width of the context toolbar when typing [AF-56] Shapes do not retain colour if selected via numerical sliders in colour chooser [AF-396] Develop Sliders are not auto enabled when expanding view or changing a value [AF-314] Batch Dialog: Hang when expanding the filetype dropdown  Tooltip for Add Custom Field in Fields Panel missing in 1971 Windows [AF-15] Tabbing out of the White Balance field collapses the group  New Batch Dialog tweaks  Curve visual not updating correctly when a node is adjusted next to a cornered node  Node Right Click context menu is missing dividers on Windows [AF-14] Edit Table Format - Amending the Fill using RGB sliders on a CMYK doc will render an RGB table preview [AF-230] Changing White Balance Temperature without enabling the White Balance section auto-collapses panel instantaneously [AF-316] Active toast when closing document with colour picker active causes cursor to be invisible  Assistant toolbar icon does not function with Settings dialog already open  Index panel is missing Show Index/and References options in Preferences [AF-21] Edit In with a passworded PDF and an adjustment fails to redraw  Pasting text in N'Ko alphabet crashes app [AF-54] Images lost when editing a password protected PDF  Hyperlink Properties' Character Style dropdown is out of view for Book Chapters  Windows Unable to drag asset subcategories around within asset category by mouse [AF-403] Brush dialog is missing the input field for brush Size [AF-380] Guides Manager contains a limit for the Spread Origin value [AF-29] On the Structure section of the Edit Table Format dialog, positions of add/delete buttons are reversed across platforms  The Table Formats panel displays formats one per row in a single column regardless of the panel's width  File partially locks up app after exporting to SVG (all pages)  Move cmd+K (Find in Layers Panel) from Misc to Layer in Shortcuts  User File crashes when changing Footnotes Notes>Initial Advance or Min Advance [AF-791] Open Template for Editing will open it as Untitled [AF-254] Flood Select Tool doesn't have the new CTRL + ALT shortcut for Add to selection [AF-601] (D) Bugs fixed which specifically affected macOS
Preserve Alpha box and label vanishes after calling dialog a 2nd time  Light UI: Scroll bar background is white which makes it difficult to see  View Mode and Insert location button groups are transparent without a document opened in Light UI [AF-22] MFA/2FA dialog shows empty grey pop up on macOS  Password protected file not loading all pages text  MacOS Keyboard shortcuts list changes depending on the selected Persona before opening preferences  Remove unwanted/missing projects from Recent [AF-203] Text Style Panel - numeric entry for colour values in sliders not possible [AF-204] Keyboard shortcut for Pixel Category > Tools doesn't save after a restart [AF-206] Shortcuts list is not Persona aware and we can set shortcuts for non-exiting actions  Drag-dropping a file from Finder inside itself shows a Recovery file warning  Recent doc previews aren't generated until after releasing scroll bar  Text Key Keyboard Shortcuts do not function on macOS Sonoma [AF-508] Anchor book mark truncates on Mac  Anchor panel 'jumps' up when editing existing anchor name, provided parent - child hierarchy group is present  New Anchor button not disabled when it should be  Text Frame > Columns doesn't update Units correctly when switching between multiple open documents  Cannot enable Show Topics in Index panel preferences [AF-328] Duplicate entries for keyboard shortcuts  Opening two .afbook files stored in different directories but with the same file name causes an app crash  Slow typing with Anchors panel and long list of anchors  Insert Hyperlink Dialog can be resized and hides Character Style dropdown  Delete cross-reference does not work across multiple stories  Editing a hyperlink to another books chapter doesn't auto populate correctly  App locks when replacing files  The Find command on a text selection's context menu is dimmed, though the command can be invoked via the Text menu  With one or more table cells selected, Font Colour on context toolbar displays a cell's fill colour  Basing a style on an existing one can set Initial Word end characters as [No Change]  Keyboard shortcuts for showing/hiding panels are in different categories across platforms  (E) Bugs fixed which specifically affected iPad
Localisation - Add custom field button has clipped text  Not asked for embedded PDF's password when opening parent document, app crashes on going to Affinity's Home screen  Names of new navigation options on View menu include the word 'page', whereas desktop uses 'spread'  Table of Contents is Toc when it should be ToC  Go to Page command affects the document view differently than equivalent desktop method  Initial Words > End Characters are not being remembered if changed from default. [AF-46] Go to Page command treats its input as spread number, not page number  If you have reported a bug and it is not yet fixed, please do not report it again. More fixes will be made during the 2.3 beta cycle.

Hi All,
Below is the list of all new feature and improvements which are included in the 2.3 beta (bug fix list is available here).
To learn more about these features please click on the link to go to each feature's dedicated post. To give feedback or report bugs against any of these features please reply to that same post (also check out bug reporting and feedback tips).
• Move Data Entry improvements
• New tags panel for adding Alt Text to images and objects
• Spiral Tool
• Ability to change Asset Panel background colour
• Fields now available in Find and Replace
• Pixel grid added
• "Keep selected" preference now available in Pencil Tool
• Create and place password protected PDFs
I should say in general we are now aiming to do slightly smaller updates more regularly than before so we can test and release in smaller chunks. This will allow us to get improvements and fixes out quicker, as well as having overall benefit to the stability of the apps.
The beta phase will now be shorter (4-6 weeks) for any update, and for that reason we will be avoiding any significant changes to functionality during beta as we focus on fixing bugs and correcting unintentional behaviour. This does mean that more of your improvement suggestions may need to wait until a future update (e.g. like some of the Move Data Entry suggestions you made during 2.2 beta which have now been added to 2.3), but please keep those suggestions coming!
Getting the 2.3 beta
If you have not enrolled into the beta program yet and would like to take part, you can do so here. This will immediately give you access to the latest 2.3 beta builds to try for yourself.
If you are already enrolled in the beta program you have two options:
1. If you still have the 2.2 beta installed, you can now run up those beta versions and you will be prompted to update them to the 2.3 beta.
2. If you have uninstalled the 2.2 beta, you will need to go back to Your Account -> Downloads and product keys and find your previous order for the Affinity Beta Software Program, and you can download the 2.3 beta from there.
Thanks,
Ash

Not sure if anyone is doing that, but yes that would not be appropriate. As someone who has led large development teams myself and worked on very large projects. It is really impossible to know from the outside what are the internal inhibitors to greater efficiency and product reliability.
Usually such matters are result of leadership, depending on size of company, but often upper management and executives. They are ultimately responsible for the operations. You can almost be certain the devs and test teams want the issues fixed as well. But they probably don't get to set the ultimate priorities.

Adobe's edge is quickly evaporating as well. Meta is now embedding AI generation directly into their social media apps and many other standalone AI generators are adding their own generative fill. The usefulness in regards to productivity can not be ignored for the users, but the business model for sustainability is going to be very challenging as any advantage is quickly lost. Thus is the nature of rapid AI development.
Therefore, my opinion in these regards is that it would not necessarily be beneficial for Affinity to spend its limited resources in a futile effort to keep up with its own implementation. They also would have to deal with as-of-yet-unresolved legal issues.
However, their scripting API would provide the necessary integration which avoids these limitations. 3rd parties and open source communities are going to be far faster at rapid innovation and keeping up with AI.

I think they do care. But marketing works on those who don't know about the bugs.
The irony is that the bugs tend to hurt the most dedicated users. The ones doing the most advanced work. For example, not many here use Artboards. I use exclusively artboards, so most don't encounter the unbelievable number of bugs that are unique to artboards. Almost all of the live filters are broken on artboards. I've been meaning to write something up about it, but haven't had the time and my motivations are low as so far no bugs I've ever opened have been fixed as of yet.