Seneca

It certainly helps getting to grips with new software if you've previously used similar software and understand the basic principles. The problem comes when people assume that the new software will have all the same features and work in exactly the same way as whatever they have used before! Of course, the other problem is when the only software someone has used previously was very basic, such as free phone apps, and they expect everything to be automated with a one click solution!

We have released a beta build to try and address a number of issues found in 2.6.3
We think a few of these fixes require some time to test them with our affected customers but we would like to release 2.6.4 to customers very soon, but it may require a number of weeks of testing.
Here are the release notes for the 2.6.4 (build 3439) beta
If you are suffering from any of the 30+ issues mentioned in that 2.6.4.3439 beta post, then please (sign up for and) install the latest beta build. If you have reported a bug and it is not yet fixed, please do not report it again. Nor can we correspond in this thread on when other bugs will be fixed (or why they are not yet fixed).
This beta is open to ALL Version 2 customers 

Here's a list of some of the bugs which have been fixed in beta build 2.6.4.3439, fixes since 2.6.3.3322
This thread is locked. To report any new bugs please do that against the relevant in this Other New Bugs and Issues in the Betas forum.
(A) Bug fixes which affected all platforms 
Lens correction for OM 12-100mm F4 not being automatically applied.  AF-7224 APO-LANTHAR 35mm F2 Aspherical II lens not identified.  AF-6408 Canon RF 70-200mm F4L IS USM lens Detected as a Canon RF 70-200mm F2.8L IS USM.   (B) Bug fixes which affected Desktop (Windows and macOS) 
User file crashing when disabling Facing Pages  AF-6808 Linked Resources- Layer visibility states are not synced when file is re-opened  AF-6647 Master page pasteboard content no longer appears on page AF-6420 Shortcut label missing in Text Style Editor.  AF-7201 Crash when double clicking Reading order panel Embedded AI files lose their data once edited User File- Pinned objects trigger PDF export failure with 'Tagged PDF' enabled Independent Baseline Grid is Not Scaled Correctly Cannot place a website image as Linked (Remote) if the image url source contains height and width information After adding a single page converting facing to non facing loses content frames Adding a single page in a facing page document shows frames in the pasteboard that should be hidden Images that are promoted and replaced on a page don't show in resource manager Crash placing a specific AI file into an embedded document Artboard Margin Colour Can't be Changed (C) Bugs fixed which specifically affected Windows 
Warped objects don't print or export to EPS as warped.  AF-450 Certain View dialogs remain selectable with no open document, causing crashes or unexpected behaviour.  AF-4003 Clicking in an Empty Layers Panel With No Document Open Crashes the App AF-6580 Opening app, closing New Document window and clicking Layers closes app.   (D) Bugs fixed which specifically affected macOS 
User File crashing when disabling facing pages.  AF-7074 Edit Hyperlink- All Hyperlinks default to first in list if the hyperlink has been inserted on a shape  AF-6660 Data Merge - Anchors names are unexpectedly appended with a number.  AF-7594 Duplicating a Page with Index Markers fails to update the Index panel.  AF-6996 User file- PDF Open/Placement causes immediate app crash.  Text Styles are Synchronising Between Open Documents.  Delete article in Reading Order panel changes order of children.  The ML Object Selection tools no longer work in the Pixel Persona of Designer in 2.6.3 Switching documents can render text at different size. (E) Bugs fixed which specifically affected iPad 
Develop persona: Overlay's opacity move together.  AF-6284 No Keyboard shortcuts for paste without formatting.  AF-631 On iPad, there's no provision to assign a keyboard shortcut to some tools Please report any bugs introduced in 2.6.4 in this forum.
https://forum.affinity.serif.com/index.php?/forum/139-other-new-bugs-and-issues-in-the-betas/
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.6.x beta cycle, and will be reported in posts in this thread.

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

This is great news. Welcome Ian. We are using Affinity exclusively at our shop and nothing is perfect. We like what it does for our clients and look forward to things ramping up and seeing what happens. My main hope is the communication is brought up a notch. Thanks again amd peace. 

Hello Affinity Forum!
I am super excited to be joining the conversation here as the new Head of Enablement in Affinity, having officially stepped into the role around six weeks ago. It’s been a fantastic whirlwind getting to know the team, the processes, and most importantly, the Affinity community.
As many of you know, things on the release and update front have been a little quiet lately. But now that I’m in this new and exciting seat, I’m really looking forward to helping get the momentum rolling again and making sure the amazing work we are doing with Affinity, and our end users, shines as brightly as it deserves to. 

Please bear with me as I get up to speed properly with comments, requests and issues. I am looking forward to sharing updates, insights, and highlights as we go. Affinity is very much here to stay - It is great to be part of this company and community! 
My background is in delivering Training to a wide network of users as well as running webinars, and events. I am happy to connect and chat to you ALL.  

I live by a simply phrase - It is nice to be nice. So let's have some fun and creative some amazing things together.

Very best 
Ian Sayers

Hey folks, 
Let me start by introducing myself...

Hello, I am Ian Sayers and have recently just started with Affinity as Head of Enablement. - check this link i have literally just posted.

I can assure you 100% that Affinity is not only still here but growing and thriving. I am only in a few weeks so give me a little more time to get my feet under the table and into the processes and working methods, then we can all have some proper fun!

In the meantime, I am happy to connect and chat (as much as possible with the million things to learn and do while joining an amazing company). reach out and connect on my social media accounts or here on the forum. Most things are found under iwsayers or just my name.

I greatly appreciate this forum and everyone that contributes in a helpful manner. 

Very best
Ian
 
 

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

We don't know what's going to happen ...
What if this? What if that? You doom mongers are exhausting!!! Do you have nothing better to think about all day?
The forum is mainly about user-to-user support. Stop flooding it with this apocaplyptic nonsense!!!

That's an opinion and an assumption, which is fine, but you state it as if it were a confirmed fact. That benefits no-one. Unless you have solid insider information, you can't know, so it's merely speculation on your part. Lack of communication and slower updates lead to fear, uncertainty and doubt. Corporate buyouts take time to digest, which I know from direct experience (at a fairly high corporate level, I might add). That's why I keep an open mind, and take a 'wait and see' attitude. 
In the meantime, the software does what I need it to do, so I use it (without an additional costly, monthly subscription). If it doesn't fit others' needs, they have a harder choice — wait and see, or look for something that does. Better communication and reassurance from Serif would certainly help, and I hope that is forthcoming. Time will tell. 
 

Only time will tell, right? There's a whole lot of speculation, (some probably fairly accurate, much probably way off the mark, but who's right?), and it seems a bit premature to announce "game over". Canva had their reasons for buying Serif, but I'm not privy to their reasons or plans. They paid too much money just to let it die...that would be stupid (which they aren't) and doesn't make much sense to me. People don't like 'not knowing', so imaginations tend to run wild. 
I'm concerned and want to see Affinity improve and succeed, but I can't predict what's coming. If the Affinity Suite is working well and doing what you need it to do at the present time, keep using it...you already bought it (and aren't paying a monthly subscription). If it's not working for you, that's a different story. Corporate buyouts (I've been through many) are disruptive, reset goals and priorities, eat up staff resources during integrating, and it takes time for things to normalize. Been there, done that! Who knows what they're working on? I don't. Maybe they have something big coming that they want or need to keep quiet. It could be really great, more of the same, or pathetic. Not knowing makes people edgy, myself included, but I'll keep using it as long as it meets my needs. Why not? Beats an expensive Adobe subscription (at least for me).
So, I try to avoid gloom and doom or unrealistic expectations, and adopt a middle of the road wait and see attitude. Time will tell.
 

@ianstudio, thank you very much for your comments.
Yes, I meant Global Layers. This is a very serious mistake in my comment because it can cause unnecessary confusion for people who do not understand the subject.
It is thanks to Global Layers that you can paste elements with remembers layers, which is very much lacking in APub. Additionally, correctly implemented Master Pages in combination with Global Layers create a powerful tool without which professional creation of publications is impossible. If we lived in times when DTP software was just being created, such an error in operation could still be accepted. However, in the year 2025, it is not only a serious deficiency that excludes APub from professional applications but also indicates a great deal of ignorance or lack of knowledge of those responsible for designing APub.
I think that Affinity Suite has great potential to become a great software. It is already very easy to use, it has many interesting and convenient functionalities that the competition either does not have or has slightly worse implementation. However, it also has many serious gaps and shortcomings that make work very difficult.

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

The developers have already announced that JavaScript is the language they are going to provide for scripting the Affinity Apps.
The also said that they are going to provide an SDK written in C/C++. If anyone wants to implement another scripting language on top of that it will be able to do so without any problem. As a matter of fact, their JavaScript implementation is on top that same C/C++ SDK. So no need for language wars. 

…The whole point of my post was to use whatever language fits your application. It shouldn't matter to me, the programmer. I should work with whatever language and paradigm the situation warrants. Limiting myself to just one language, refusing to learn or work in multiple languages, is what I'm criticising.
When writing an OS, use C or C++ or Rust or something. When writing a web app, don't whine about not being able to use C. Just use whatever is available and suitable. Switching between languages shouldn't be a big deal.

InDesign's "Span Across Columns" is a great feature, but you can't control which column the span should start from. It always starts from the first column.
"Split columns" must be added to Publisher, too.

The only way to avoid duplicating styles while copying text from one document to another is as follows.
Let say we have 2 documents with same style names, that differ in font size or font name, etc. and we want to copy some text from document-2 to document-1.
What needs to be done is as follows:
1. Open document-2.
1. Import styles from document-1 to document-2. Any styles with the same names in document-2 will be updated to the styles in document-1. 
2. Copy text from document-2 to document-1.
3. Close document-2 without saving.
The copied text will not create duplicate styles.
It's important to note that the text in both documents should be clean, no manual overrides.
I've been using this workaround for years but I hope that this bug/misfeature will be fixed soon as this slows down my work tremendously.
 

The only way to avoid duplicating styles while copying text from one document to another is as follows.
Let say we have 2 documents with same style names, that differ in font size or font name, etc. and we want to copy some text from document-2 to document-1.
What needs to be done is as follows:
1. Open document-2.
1. Import styles from document-1 to document-2. Any styles with the same names in document-2 will be updated to the styles in document-1. 
2. Copy text from document-2 to document-1.
3. Close document-2 without saving.
The copied text will not create duplicate styles.
It's important to note that the text in both documents should be clean, no manual overrides.
I've been using this workaround for years but I hope that this bug/misfeature will be fixed soon as this slows down my work tremendously.
 

This feature was discussed at length here in this forum. Just search for this term.
It's not a must because not all competing programs have it, QuarkXPress is one of them.
On the other hand a lot of people would cringe at the fact that people distort glyphs (scale them ) to achieve as you call it precise justification. 

Maybe there's little activity on the forums from everyone at Affinity/Canva because they are all working on something big, something really big, something really, really, really big.
 

I don’t think it’s a generational thing, but rather an overall change in consumer expectations. In the 90s and early 00s all updates, fixes, new features, etc were generally saved for the next big release (every 18-24 months typically) so that they could be burned to CD-ROM (remember ‘gold masters’), packaged in a shiny new box and sold to consumers. Sure there might be minor updates along the way for critical bug fixes and minor updates, but these were often inconvenient for customers due to limited internet connectivity and bandwidth concerns. 
Over the last 20 years with the web and app stores customers have come to expect a constant stream of incremental updates. While this is great when you have a mature, stable product and are able to continually drip out minor bug fixes and small improvements every couple of weeks, it does pose a significant problem for less mature or less stable products when they need to implement significant changes in their product. These types of foundational changes can take months or even years (ahem, especially with mounting technical debt) to complete, and in the current culture of constant updates these products can often feel stalled or abandoned by their customer community.
Serif isn’t the only company with these issues today, Procreate has also faced similar criticism from their community for a lack of meaningful updates. Recently however the company changed from their default mode of radio silence (it’ll be released when it’s released) to a more open dialogue with their customers, providing them with an indication of what they’re generally working on, what issues they face, and rough estimates of when users might begin to see that work released. This strategy appears to have been a very smart move as it has greatly reduced customer frustration along with rumours and speculation about the death of Procreate, or whether or not the company is still actively engaged in its development.
Anyway, I’m sure the staff at Serif are still actively working on the Affinity suite, and no doubt both they and Canva have big plans for the software in the future. One thing they really need to develop however is a clear communication strategy as the ongoing total radio silence and the popular “it’ll be ready when it’s ready” narrative look jarringly out of place in today’s consumer market, and continues to erode consumer confidence.

Agreed, "now" lagging behind doesn't make sense, since they have been lagging behind in some capacity or another from day one.  Both of the other products have been around much longer and have had more time in which to develop.
That doesn't mean the "newcomer" is doomed to fail or to always be behind - there are likely many users for which the Affinity products are a better choice for one reason or another, even ignoring cost or pricing model.  Different types of projects, different tools that work better for them.