deepblue

Hi Deepblue, are you using the Colour Picker Tool from the Tools Panel on the right hand side? It sounds like the behaviour you're seeing is By Design.

That tool has 'Apply to select' enabled by default, so the colour you're picking is immediately getting applied to your placed image. You can disable this then it will not apply to your image.

Alternatively you could also look into the Colour Picker on the Colour Panel. That lacks a colour of features that the Tool has, but allows you to immediately pick a colour from a pixel and places it in its own 'well' in the Colour Panel that you can then click on to set as the active colour.

Hi @NotMyFault,
Thanks for your report and our sincerest apologies for the delayed response here. We are exceptionally busy following the release of V2 and we thank you for your continued patience and understanding here.
I can confirm this issue was already logged for Windows, however I've been able to replicate this on macOS with Retina Rendering set to High Quality, even on an Intel based mac.
Therefore I will be updating the development log with this information and 'bumping' it with your thread now

Please see my post above, as sansnom has requested this and I've explained the current behaviour, based on the thumbnail size the Affinity document generates.
I'll be sure to add your vote to the feature request described in the above post

I find the transparency grid when exporting PDFs quite annoying, partcularly if I'm trying to check some fine detail. It's a shame there isn't an option to show it as white (or something else). An option to hide the preview would be good.

An option found in other graphics software, yes, this would bring real convenience to users, especially on large screens. Come on, a little effort!... Thank you to the whole team... 🙂

Can you also ask your team to maximize the macOS Finder Quicklook preview window!... 😉

Hi @norbinw,
It wasn't 3 months. Developers and staff also needed to rest and enjoy Christmas/New Year celebrations with their families. I was trying to address your comment/feedback about v2.0.4 specifically and what it was about. It doesn't mean it was everything we have done during this period. Some issues other than the fixes included in that build also did take time to sort out: the app's activations proved to be more tricky than expected and required some code revisions; the negative feedback towards the MSIX package format also required to build and test new EXE files, a new content package ( for V1 users who upgraded to V2 as a thank you for their support) was also prepared/tested during this period; several bugs more were fixed but weren't ready or considered safe to be included in the first patch (still have to go through QA), etc.

It's true there was a bit more bugs than we hoped for - quite a few due to the improved/changed UI - but we are addressing them as quickly as we can. A broader/public release also brings up issues that weren't detected during internal testing. V2 however fixed a few old V1 bugs.

The price of the app doesn't always sort everything out - there must be a balance here. And the sad/untrue comment about the developers was unnecessary - they are quite good/qualified actually. The issue is finding more like them. We have been and still are looking for/hiring more developers for months (years?) now.

my last post. I’m posting on instagram (yuk) and twitter (2 followers so Elon will be getting worried!)  if you can find me! Also in the private Facebook Affinity Designer group (the biggest one).
Two quick ones. Did the astronaut then he had to have some transport. The rocket is a bit closer to futurist I guess. Rocket one needs a tweak or 10 but didn’t take too long.
 
 
 
 
 
 
 

@R C-R,
The bug affects both OS's - Mac and Windows. I moved it to the Bugs in the macOS section because that's the OS @catlover is using and because there's no section in the forums that includes both OS simultaneously so I had to pick one but the report is filled against both. When you set a palette as default (for a specific colour-format) the app does create a "new" document palette (based on that default palette) that's placed above all the other palettes listed - you have to scroll up a bit to see it. Hopefully the video below will make it more clear. Of course you have to create a palette first (or use one of the existing ones) and set it as default for the colour format you want, only after that all documents that use that colour format will have that palette available (although not selected by default - which is what's logged as a bug).
palettes.mp4

That’s fine. Just move onto other software then if you’re not willing to help debug and work with developers on software that is a massive value (for a reason and with caveats at times). You don’t need to constantly announce your departure. 

Hi @BruceFerjulian,
There a misunderstanding going on here. The original issue reported above refers to the Inpainting Brush Tool (and other brush tools) reverting to an arrow cursor after first use (no matter where the cursor was located). This was indeed fixed in v2.0.3.321. The issue you are referring to which is placing a brush tool over the scroll bars specifically (preventing you from seeing the cursor to manipulate the scroll bars) wasn't addressed and as far as i can see (I'm double-checking) is not logged anywhere. I will do so incase I can't find any report.

[EDIT]This issue is indeed logged but wasn't fixed/addressed yet. I've updated/bumped the report to bring it up to devs attention again. I'm sorry for the delay and inconvenience this is causing you. Thanks for your patience.

We are pleased to announce Affinity Designer 2, Affinity Photo 2 and Affinity Publisher 2 are now all updated to version 2.0.3 (for all existing customers on all platforms).
Here are links to the release notes
Affinity Designer 2.0.3 for Windows               ( Microsoft Store and Affinity Store ) Affinity Designer 2.0.3 for macOS                  ( Mac App Store and Affinity Store ) Affinity Designer 2.0.3 for iOS                        ( Apple iPad Store )
  Affinity Photo 2.0.3 for Windows                    ( Microsoft Store and Affinity Store ) Affinity Photo 2.0.3 for macOS                       ( Mac App Store and Affinity Store )  Affinity Photo 2.0.3 for iOS                             ( Apple iPad Store ) 
  Affinity Publisher 2.0.3 for Windows              ( Microsoft Store and Affinity Store ) Affinity Publisher 2.0.3 for macOS                 ( Mac App Store and Affinity Store ) Affinity Publisher 2.0.3 for iOS                       ( Apple iPad Store )  Please follow this thread here to get notified when any new releases are made.

Would absolutely love to have this function. It would make our workflow so much easier. We resort to using Scribus (and the UI for that open software is clunky and not easy to use...) because we'd rather not pay a subscription to any alternatives. Was surprised to see it wasn't implemented in V2 after seeing so many requests for it for V1. Surely if open software can accomplish it the team at Serif can do it too? 

We work with clients around the world who do not always have access to printers or scanners. Form fillable PDFs are a big part of improving the accessibility of the products we create and sell. We know plenty of others in our industry who would happily leave Adobe for Affinity if Publisher could accomplish this.

I want to create table (16x3) by Affinity Designer2, I can't find table icon to start table.  where is icon?

Good option! I noticed you can also copy a table from Publisher and paste it into Designer if that's a better workflow for anyone. Seems to retain all the functionality. Maybe down the road they'll include tables in Designer. (Although it's typically not the place to work with tables, I can see uses for it.) That said, I love that owning the full suite/universal license that allows this is affordable.

In Designer, none specifically that I know of.
But if you have Publisher, can open the document there…create your tables and switch to Designer Persona to work.
 

Thanks for providing that for me! 
I've been able to reproduce this with your files on a USB drive set to EXfat, so I'm logging this as a bug with our developers now as these resource files should not be visible. 
Thanks for your report

Some relevant links and information that may help others understand and troubleshoot.
https://www.w3.org/TR/SVG/coords.html
https://www.w3.org/TR/SVG2/coords.html
SVG settings on File > Export...
For PDF, SVG and EPS file formats:
Rasterize—select an option for rasterizing design elements which are unsupported by the file format. Select from the pop-up menu: Nothing—no elements within the design are rasterized on export, therefore unsupported elements are not included in the exported file. Everything—all elements within the design are rasterized for a resulting exported file which perfectly matches your original design. Unsupported properties—only unsupported elements are rasterized in the exported file. Downsample images—select whether to downsample raster images within the design. Above—if this set DPI is exceeded by raster design elements, those elements will be rasterized down to this set DPI. This option is dependent on the Downsample images option being active. Use document resolution—ensures the export is the same DPI as the current project's setting. Use DPI—overrides the current project's resolution setting for the export. The exported image's DPI is set using the adjacent input box Allow JPEG compression—when selected, rasterized design elements will be compressed to decrease exported file size. If this option is off, rasterized design elements will be exported as uncompressed. For SVG file format:
Export text as curves—when selected, the text in the resulting file will be drawn as curves (therefore displaying precisely as intended, even if viewed on a device without the used fonts installed). However, this option will increase file size, and text won't be editable as text or available to "text to speech" in other apps. If this option is off, text will be exported as text and the viewing device will need the used fonts installed for it to be viewed correctly. Longer text spans—when selected, text is placed relative to previous lines of text (therefore producing smaller file sizes and simpler file structures). If this option is off, text is placed with absolute coordinates. Use hex colours—when selected, colours in the exported file are expressed as RGB Hex values (therefore reducing file size but less human-readable). If this option is off, colours are exported as standard RGB values. Flatten transforms—when selected, transformed objects are 'fixed' in the exported file. This allows for the file to be viewed more accurately across applications. If this option is off, objects remain dynamically transformed to allow for more flexible editing. Use tile patterns—when selected, rasterized areas may be converted to a vector shape with a filled bitmap to give smoother, sharper edges. However, this might not be supported by some apps. If this option is off, objects will exist as singular elements within the exported file. Set viewBox—when selected, the exported file includes coordinates and dimensions which define the view box of the image. If this option is off, no view box data is included in the exported file. The export area is used to define the view box. Add line breaks—when selected, the code in the exported file will be optimized for human viewing and reading. If this option is off, the image will be exported with code on a single line which will make the file size significantly smaller. For SVG and EPS file formats:
(Use) Relative coordinates—when selected, objects in the exported file have relative positions for maximum editability. If this option is off, object positions are fixed to create a file which is optimized for viewing.  

Hi Ash,
my sincerest congratulations to version 2 of the Affinity suite, to you and the entire team, and thank you for your explanations! The new version offers great improvements to the entire application suite, and the new solutions you found are extremely well thought out. 😀
Keep up the good work! And if I may add this here, I would really love to see improvements in the “little things” along the version 2 development cycle. By “little things” I mean those usability improvements that save us clicks in frequently performed tasks, most of which have extensively been discussed on these forums. Such as
Alt+drag to copy objects in the Layers Panel, Alt+click on layer’s or group’s triangle in the Layers Panel to open or close the entire subtree structure, as it is the case in macOS Finder, Shift+drag to constrain the aspect ratio of the Crop Tool rectangle in Photo, the option of having the Crop Tool remember its last-used state (make it a preference, if you don’t like to make it the default behaviour), the option of setting a custom default tool for an app and for embedded documents that are opened in a new tab (Photo, for instance, always defaults to the Hand Tool which is of no use if you have a trackpad), copy & paste of slices in the Export Persona, the option of adding the Snapping Options Buttons to the toolbar of the Export Persona, the option of holding down a key to temporarily activate a tool just until key release, the option of moving selected pixel content with marquee tool and Command key pressed, etc. (… I’m sure you’ve compiled a list of these little things over the years yourself …) None of these improvements should really be controversial, overly difficult to implement or break any existing workflow. At the same time, their absence is felt every day and slows down workflows considerably, especially when taken together. Sure, it’s unlikely that you win any new customers by adding such options (alone), but you will make a lot of existing customers happy. Now that you have all three apps up and running on all target platforms, I think it would be a great time to add these “little things,” and it would add additional emphasis on the fact that you care for your user base … 😀
Again, thank you!
Alex 😀

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

Hi there,
Since Affinity has been very quiet lately, I wanted to ask when the next beta version will be released.
Is there a page that tells what new features are planned for AF Designer and AF Photo?
Or which problems were fixed in the Mac version?
I would be very happy about some information.
Thanks very much

Hi there,
Since Affinity has been very quiet lately, I wanted to ask when the next beta version will be released.
Is there a page that tells what new features are planned for AF Designer and AF Photo?
Or which problems were fixed in the Mac version?
I would be very happy about some information.
Thanks very much

Today I updated my MacMini M1 to Monterey 12.3 and I have to say that the programs Affinity Designer and Affinity Photo start much faster.
I now work with Affinity Designer almost every day and am very happy with it for my stuff.
I'm looking forward to the new version of Affinity Designer and Photo and I hope I don't have to wait too long.

Thank you Walt for your quick reply. 😊  Too bad there is no active communication with Affinty. Have an Apple MacMini (M1) silicon with Monterrey and there are a few issues that have been addressed here on the forums. The problems were probably collected and forwarded to the Affinity programmers.
It would have been nice to know which problems have already been fixed.
OK, I'm very happy with the programs AF Designer and Photo. I'll just wait until there's a new version.
Thank you again.
Many greetings
Mark

This is of course not "outside of the app". The feature to show a good preview of a file in the finder is called "Quick Look":
https://developer.apple.com/documentation/quicklook
Unfortunately, Affinity Photo or Affinity Designer do not provide this extension and all you get to see is a small png of your photo or designer file in the finder. It's not a bug, but the unwillingness to properly implement a very useful standard feature of Mac OS.