000

https://affinity.help/publisher2/en-US.lproj/pages/Media/linkedServices.html
 

I really do like version 2 of all three apps -- I do believe though it would have been good for the software to go through a public beta cycle, same as version 1.
While I have not found any ,showstoppers' and the software runs stable for me, I already filed four or five bug reports during the past few days; This is way more than I ever encountered in the later stages of version 1.
I'm keeping my fingers crossed for one or two hot fixes and for future updates that (in additon to new features as promised) also fix these  things that are slightly cracked (not broken, just ... a bit annoying).

I really do like version 2 of all three apps -- I do believe though it would have been good for the software to go through a public beta cycle, same as version 1.
While I have not found any ,showstoppers' and the software runs stable for me, I already filed four or five bug reports during the past few days; This is way more than I ever encountered in the later stages of version 1.
I'm keeping my fingers crossed for one or two hot fixes and for future updates that (in additon to new features as promised) also fix these  things that are slightly cracked (not broken, just ... a bit annoying).

I'm finding the Ctrl > Drag Duplication a bit glitchy compared to V1. 
Some of the FX feature tend to lock out and not allow changes.

Hi,
I noticed that some of the buttons in the new UI are a bit too small to click them quickly -- it takes another second or so to identify and find the exact point of where to click. While it looks super neat and needs less screen space than in version 1, I preferred the slightly larger, easier to click buttons.
Espiecially the up/down arrows in the Character and Paragraph panels are tough to ,hit' when I'm in a hurry and these are button I need constantly, so they need to be easily clickabl without consciously "aiming" each time.

I have encountered several cases where the ,Find' feature did not find strings of text I could easily find in the document with "search" feature of a free PDF viewer. This usually occurs when searching for several strings in a row (e.g. search "string1", then "string2", then "string3" and so on) ... at some point the software just stops finding things.

I also find Designer a bit too prone to crashing when zooming and panning in a 500mb document.

I really do like version 2 of all three apps -- I do believe though it would have been good for the software to go through a public beta cycle, same as version 1.
While I have not found any ,showstoppers' and the software runs stable for me, I already filed four or five bug reports during the past few days; This is way more than I ever encountered in the later stages of version 1.
I'm keeping my fingers crossed for one or two hot fixes and for future updates that (in additon to new features as promised) also fix these  things that are slightly cracked (not broken, just ... a bit annoying).

It's not because of when you created the bleed. It's because in the 2nd case you have an Artboard. Objects in the Bleed area of an Artboard do not show; they only show on the Artboard. Or entirely off the Artboard.
Long-time bug from V1, still not fixed.

I'm not from Serif but yours is the second post I've seen with this same screenshot of a messed up Account/Recent Files panel, where you have a combination of the Recent Files and Account panels at the same time and with no recent files shown. To me, it looks like Affinity has either saved or loaded its new document / recent files panel data incorrectly.
This is not a supported approach but I've done this several times myself so if you want to try it go ahead but if you're unsure you should wait for Serif to respond.
Quit Publisher 2 Using Finder, open: Macintosh HD/Users/<username/Library/Application Support/Affinity Publisher 2/ Delete the files: newdocumentpanelstate.dat mru.dat Start Publisher 2 Deleting these files should clear out your settings for New Document and Recent Files. If you'd changed your default paper size from A4 to Letter it will be back to A4. If you had recent files in your menu they will be gone. If this doesn't fix it, then you'll have to wait for Serif to provide assistance.
Good luck!

Hi @Jens Krebs, I use these buttons rather than scrolling through menus

The contrast of the arrow button in the new UI is a bit low.
It is great, that one can adjust the contrast for the TEXT, but this should apply to the buttons / arrows as well in my opinion.

Hi,
I noticed that some of the buttons in the new UI are a bit too small to click them quickly -- it takes another second or so to identify and find the exact point of where to click. While it looks super neat and needs less screen space than in version 1, I preferred the slightly larger, easier to click buttons.
Espiecially the up/down arrows in the Character and Paragraph panels are tough to ,hit' when I'm in a hurry and these are button I need constantly, so they need to be easily clickabl without consciously "aiming" each time.

The contrast of the arrow button in the new UI is a bit low.
It is great, that one can adjust the contrast for the TEXT, but this should apply to the buttons / arrows as well in my opinion.

😅😂👏
great britain 😅 

Hi All,
Well, it’s been a pretty crazy week since the launch of V2!
This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
Updates to V2 moving forward
Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
Updates to V1 moving forward
While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
We will update our FAQ shortly to make that clearer for everyone.
Offer period
In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
Upgrade pricing
It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
A comment on no subscription
I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
All the best,
Ash

It just works as you would expect. Add your index markers in each chapter file. Insert your index into the last chapter file and it will create an index based on the markers in each chapter.
The only thing to keep in mind is that Index Topics aren't synced between chapters, each chapter just has the topics created in that chapter. Let's say you index Oranges in chapter 1. If in chapter 2 you decide to index the same word Oranges won't be an existing topic in that chapter so you're effectively creating it again which is fine but Oranges won't be in the dropdown of existing index topics. So perhaps you might forget what you did last time and index it as Orange this time instead of Oranges.
If you take an existing book with an index and break it into separate chapters it then each chapter would initially have a complete set of topics but just the markers for that chapter. So looking at the index panel might be confusing because you'll have a lot of topics without markers. That's okay and you could delete the extra topics from each chapter if you wanted to.

New welcome screen is great too

I can finally place child layers correctly instead of Designer/Photo thinking I wanted to make them into a mask. So much easier to toggle lock and visibility on layers. The Style picker and copier!

Non-destructive RAW editing Drag-n-Drop Image files into color wells Shape Builder Tool

1. AP: Non-destructive RAW development (did someone mentioned the Ger..., DAM? 😁)
2. AD: Measurement tools (addition of document persistency would be highly welcome, though)
3. Universal license (even though this requires online activation)

All on Photo.
 
1. The new masks
2. The new live filters
3. It just runs better

1.transform links  aka chain links in Psh
2.hide vs hide others  working together with "select same tagged"  , smells like layer comps of a sort.
3. Displace live fixed , not quiet yet although . Still no control over displace direction .      Still can be used as a slope blur  from Substance designer  (with macro recorded)
 

As an iPad user
1. StudioLink
2. the ability to apply Palettes in Color Overlay
3. the ability to apply transparency over Styles (this didn’t work with the halftone styles I work with)
2 and 3 are very specific improvements but they make a huge difference to my workflow now.

1. Publisher auto place for images
2. Photo live mesh warp (still need hold shift for constraint to be implemented)
3. Photo multiple Layer FX