vonBusing

Then don't use PSD. Use SVG or EPS as VIPStephan suggested, or PDF. These export formats support text.

Because it's a total nightmare.  Getting our text export to be identical in Photoshop is no small task.  To make it editable and precise requires very detailed knowledge of how Photoshop handles text - and that is knowledge private to the Adobe dev teams.  We have to work it out for ourself.
 
We have a big enough job getting text import to be accurate.  Import is our priority - it has been stated many times that we do not intend Affinity to be a stepping stone in an otherwise Adobe tool chain.  There are many reasons to work within the Affinity ecosystem and use the end-target export options for collaboration in web and print.  Round trip between PSD and Affinity is not a 1-to-1 process.  Data has to be converted, sometimes in a way that cannot easily be reversed.
 
Editable text export will happen one day.  We are concentrating on other priorities first.

Hi Herojas93,
The feature you have highlighted is different from what you are trying to do.
There's no way to hide the canvas of the Artboard directly in the document as you want.
 
 
 
This new feature allows you embed a multiple artboard document (like yours with four artboards) into another document and then choose (in the context toolbar) which of the artboards you want to have visible in that embedded document. Previously all of them were visible in the embedded document, now you can choose which artboard you want to have visible.
 
Here's an example:
I've created a document with four artboards and placed their respective number in each one of them for identification purposes then saved as document_with_four_artboards.afdesign
 

 
I've then embedded this afdesign document in a new one (menu File ▸ Place). See the Layers panel. In the context toolbar (with Move Tool selected) you can now select which artboard you want to display in the embedded document: in this case i've selected Artboard2 (highlighted in red).
 

 
 
 
 
 
 
 
 

Did you just say "Batch Processing", Andy?
Won't be able to sleep until the beta is out ... please hurry ;-)

Hi,
 
AP 1.5 beta is coming - in a couple of weeks or so.. here are a few of the things we can look forward to:
 
- HDR merging.
- HDR toning.
- Full 32bit unbounded linear editing, including (correct) OpenEXR, Radiance support.
- Focus merging.
- Live Projections (edit in perspective projection, equirectangular projection).
- Macro recording and playback gallery.
- Batch processing.
- Layer linking.
- Magnetic selection tool.
- Polygonal selection tool.
- Ability to round-trip PSD (for use with DAM applications).
 
- Lots of small improvements.
 
Hope this helps,
 
Andy.

Not really; it's the issue I mentioned, of embedded documents always being rasterised. This should be fixed in 1.5, when that comes out.

Interested but more looking forward to Publisher.

Wow! You guys are eagle-eyed!!! :O  There's a LOT of bits and bobs and a number of big features - I don't think the 'sneak peak' shows off our symbols very well at all - they're far more feature rich than any others I can find... :)

The beta looks for the MAS and so the MAS is the "key" for the beta to work.
The every MAS has a different key (maybe the beta just creates a hash from certain parts of the MAS install?).
Anyway, the current MAS is as new if not even more up to date than the latest beta so in theory there should be no need to access the beta.
 
One valid problem I see though is that the beta descriptions states "This build should be considered more stable than the current MAS version (1.4.1) and should be used in preference to that build."
- if people follow that rule and build presets etc. in the beta, they now loose access to those presets which is unfortunate.

Any shape can be used as an Artboard. You might want round ones for DVDs, CDs or records, for example.

This post makes me wonder if all the Affinity community shouldn't deliberately send their print projects first wrong then how they need it the second time. It would create a buzz with the printers that they may need to add this inexpensive app to their computers. Hmm... Could it work?

Thank you for the swift reply but surely this should be fixed before general release as its a feature that must be used often?
 
Or am I living upto my name?
 
Regards
 
Crambazzle
 
"A tired and worn out old man"

Hi smallreflection,
 
Just trying to make sure there's no misunderstanding - we now move guides around with their artboards and duplicate them with their artboards, the only thing we don't do (which I have obviously overlooked) is when you create the first artboard in a non-artboard document I am not taking the current guide setup and applying them to the new artboard. Is this such a frequent problem that it can't be worked around (i.e. by just making the artboard in the first place?)
 
I'll obviously try my best to add this extra and re-upload if I can do it safely, but I just wanted to make sure that you knew the current state of play...
 
Thanks,
Matt

Purpose: Fixes
Status: Release Candidate
Requirements: Purchased Affinity Photo
Mac App Store: Submitted
Download: Here
 
To use this beta, simply download the file from the link given above and double-click on the file to open the installer. Follow the instructions to install the beta version. The beta sits alongside the Mac App Store version and will not interfere with it.
 
This is a release candidate build. It has been submitted to the App Store for review and we will make it available as the current App Store version when we are confident there are no unexpected problems. This build should be considered more stable than the current MAS version (1.4.1) and should be used in preference to that build.
 
Fixes
 
- Fix for converting between wide-gamut RGB and sRGB profiles causing incorrect colours
- Fix for converting colour profile/colour model not undoing correctly for inner glow effects
- Fix for occasional crash with arrow shape
- Fix for Rasterise causing layer effects to appear the wrong size if they were present on a scaled object
- Fix for A1 (Press Ready) preset having the wrong dimensions for an A1 sheet (*sigh*)
- Fix for tool shortcut keys on international keyboards
- Updated help file
 

Purpose: Fixes
Status: Release Candidate
Requirements: Purchased Affinity Designer
Mac App Store: Submitted
Download: Here
 
To use this beta, simply download the file from the link given above and double-click on the file to open the installer. Follow the instructions to install the beta version. The beta sits alongside the Mac App Store version and will not interfere with it.
 
This is a release candidate build. It has been submitted to the App Store for review and we will make it available as the current App Store version when we are confident there are no unexpected problems. This build should be considered more stable than the current MAS version (1.4.1) and should be used in preference to that build.
 
Fixes
 
- Fix for converting between wide-gamut RGB and sRGB profiles causing incorrect colours
- Fix for converting colour profile/colour model not undoing correctly for inner glow effects
- Fix for occasional crash with arrow shape
- Fix for Rasterise causing layer effects to appear the wrong size if they were present on a scaled object
- Fix for A1 (Press Ready) preset having the wrong dimensions for an A1 sheet (*sigh*)
- Fix for hairline artefact visible on vector brush strokes around the line cap
- Fix for tool shortcut keys on international keyboards
- Updated help file

Seems it have worked Rui: Affinity Designer Customer Beta (1.4.2 - RC1) has just been released.
Maybe if you continue punching holes in the refresh icon, version 1.5 will come out too :)

Hi everyone,
 
The reality is what I've described elsewhere: People use our beta versions for production work because they have traditionally been stable and supported. This is great, but also causes us a potential headache: If I make a major architectural change (like Symbols, which is just one of the new features that you know are coming) and then I release it as a beta and people use it for important work then I have to support that architecture even if I change my mind and want to do everything differently. This leads to us having a huge lump of code hanging around forever to support a thing that was only available in one beta version. This is very bad. So I basically can't release large features to beta until they're ready - and by that I don't mean 'utterly perfect', I just mean that they're definitely the right way to do things. Sometimes you only find out limitations or drawbacks by trying things... Right now our Art Director and MD are playing with 1.5, planning their videos and giving me feedback so I can assess whether the required functionality is there and whether there's anything fundamentally wrong - that basically means there's not so long to wait now until 1.5 is ready for a beta release (unless they tell me something horrific in the next few days - which I don't think they will!)
 
As to why the 1.4.2 betas have been slow to appear - basically everyone is spending the bulk of their time getting 1.5 ready. This is good and bad. If they weren't doing this then there would be a big gap between 1.4.2 and 1.5, whereas the gap should now be short, but it does delay the release of 1.4.2 - but 1.4.1 (MAS) is pretty stable and the 1.4.2 beta that we have resolves most problems already if a user encounters one, so the only thing people are really missing out on is a 1.5 beta... which as I said, is approaching faster because there's been more developer input to it than to 1.4.2.
 
We have tried to add a number of big things in 1.5 and if this makes people unhappy about the update frequency (because big features cannot be released in a state where we're not 100% confident the architecture is correct) then we'll have to give only one big feature each time (which may not appear in the beta until a few weeks before the end) and a number of smaller ones. We're obviously listening and learning what you're all after throughout this process - so we can hopefully deliver more of what you're after next time. But I have to say, when you see 1.5, I don't think you'll be complaining about the new features... ;) 
 
Thanks again,
Matt

And the Lord saith: Thou shall atone for thine sins by releasing another beta soon. And 1.5 beta. And, like, ehm..., Publisher... ;) (seriously, I have been waiting for that one for ages and had to buy both Designer and Photo just to endure the pain... Addictions can be funny - turns out I am addicted to something I have never seen or imbibed yet. :rolleyes: )

But You guys made us (AD users) "every friday new beta" addicts! And here You go, these are the consequences - stack of addicts with discontinuation symptoms :-) Me included :-/
We are nervous, impatient, looking for culprits… WHERE IS MY BETA!!? :-)
 
Seriously, You should start the AD detox. Or be very carefull about given informations. Someone send echo here at forums, that 1.4.XXX new beta would be shipped last friday :-( That is torturing!

-

We are going to make a professional Affinity DAM application - stay tuned in 2016 for more information ;)
 
Thanks,
 
Andy.

In the "Document" menu, there is an "Transparent Background" that toggles white/transparent background.

Hi markw,
 
Have a look at this site, it outlines what makes up PDF/X1,2 files, hopefully this will help you decide if you need to export using one of these presets.

PNG-24 (with transparency) - currently there is no option to output without transparency.
 
Some of my destinations (apple app store) can't take PNG-24 with an alpha channel. I currently have to use a photoshop batch to remove the (100% white) alpha channel. 
 
A checkbox to include alpha might be useful. 
 
btw - I can use j-peg instead in this instance but I prefer to use png - having greater control over what comes out of AD is always going to be a win.

Thanks Matt.  
 
You make really good and convincing points in your response and that clarifies for me the challenges that are delaying the release.    I do understand the importance of architecturally getting things right before releasing it to the public.  
 
Thank you so much for you dedication to working on this product and I hope you don't spend all weekend writing code :)   Have a good weekend.
 
Nana