DarkClown

Regardless ... Its got beautiful plumage!

Those were not the impatient ... those were the grumpy
But I guess your assumption is most likely right ... and knowing about state of development will not increase the speed ...

Or to say it cinematic:
 

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

I guess most people expected that. Nevertheless it may help the impatient among us if you give a rough timeline when to expect news

I can confirm that it is the cropped group causing the issue, attempting to export a cropped group will ignore the crop shape on the group and will export the entire selection. This issue is currently logged with the developers for resolution.

Hi @DarkClown,
Feel free to upload your file to the below private dropbox link if you don't feel comfortable sharing here and we'll investigate further. 🙂
https://www.dropbox.com/request/QjfmPuewWwQwp4bUnseD

I wonder if the photoshop 8bi (additional file format) support is planned in the future. This would resolve some of the often discussed issues with non-suported file formats e.g. WebP since 8bi PlugIns are available already. 
Cheers, Timo

It's been more than 2 years people are requesting support for variable fonts. I'd like to bring this topic up since it seems not getting any attention. Of course this affects all Affinity products and not only Affinity Publisher.

And if basic font support does not make it to the essential feature requirements please make sure to handle this failure/bug with a bit of dignity (even Photoshop 6 disables the styles for variable fonts and does not display random nonsense)


 
Cheers, Timo

Yep, that caused it ... I had the node tool active and that caused the issue - works fine with the move tool. Same for the transform panel as well as the layer menu entries. Hard to undestand why transformation is not available with a different tool since it is a global layer operation. But obviously my mistake.

Thx Walt!

Thanks. For the Transform panel, make sure you have the Move Tool active. (Not at my computer at the moment, so can't try it myself, but that has caught me before.)

This is a valid point. Just as a suggestion for an easy to implement intermediate (or maybe even final) solution: Why not include a checkbox in the export dialog that will automaticall open the exported file in a new document in AP for further devekopment?

Ohh, don't bring up the old stuff ... Only gets me into trouble. I always get a shitstorm for reposting
But frankly spoken I had the impression that 5 years gone by justifies to put up a little reminder .... and we are not asking for functions to construct frequency separated intersections between penguins and octagons.
<sarcasm on>
And I guess it's still a huge surprise for serif that there are people out in the world that try to productively use their tools
<sarcasm off>

But as I said - let's hope for AP 2.0

@DarkClown I fully agree with you — it would be nice to have a kind of output sharpening parameters section somewhere in export options. Having to go through multiple rounds of exports seems very inefficient.
Btw, I found your thread from 2017 with the same question: 
Unfortunately, it seems like nothing has changed in this regard.
Hopefully we'll see some improvements in next versions.

OK, thank you.
It's not what I would call a proper "workflow" .... more something like a "workaround" 🙂 ... Let's wait for AP 2.0

Hi guys,
I'm wondering what would be the optimal workflow whith regards to sharpening when you try to export (Exporting through the Photo Persona) a JPG from an existing picture? When I work on high res photos of course I don't want to resize the original before output to be able to properly adjust the sharpening settings for the required output resolution. On the other side a proper judgement of sharpening can only be done in the final resolution. The export dialog where you enter the output resolution does not allow setting the sharpening parameters for the entered resolution. I don't see a proper way in the export Persona either.

For proper adjustment I would need all sharpening parameters and a 1:1 pixel precise view in export resolution. To me this seems to be a quite commen process. How do you realise this in Affinity Photo? What is the recommended workflow.

Cheers, Timo

Even though we should stick to the original thread and I do not agree with creating the duplicate, variable fonts mess is kinda weird and annoying. Adapting the concept of variable fonts is one thing but treating them like users does not have them installed or they do not exist is another

It's been more than 2 years people are requesting support for variable fonts. I'd like to bring this topic up since it seems not getting any attention. Of course this affects all Affinity products and not only Affinity Publisher.

And if basic font support does not make it to the essential feature requirements please make sure to handle this failure/bug with a bit of dignity (even Photoshop 6 disables the styles for variable fonts and does not display random nonsense)


 
Cheers, Timo

Will do so!

It's been more than 2 years people are requesting support for variable fonts. I'd like to bring this topic up since it seems not getting any attention. Of course this affects all Affinity products and not only Affinity Publisher.

And if basic font support does not make it to the essential feature requirements please make sure to handle this failure/bug with a bit of dignity (even Photoshop 6 disables the styles for variable fonts and does not display random nonsense)


 
Cheers, Timo

It's been more than 2 years people are requesting support for variable fonts. I'd like to bring this topic up since it seems not getting any attention. Of course this affects all Affinity products and not only Affinity Publisher.

And if basic font support does not make it to the essential feature requirements please make sure to handle this failure/bug with a bit of dignity (even Photoshop 6 disables the styles for variable fonts and does not display random nonsense)


 
Cheers, Timo

In case serif considers implementing this feature of course developing and testing is involved (I'm happy to support) - so surely programming is required - but no commenting. Action speaks louder than words

They would look at the number of posts in that topic, and who made them.

Unless, for example, you're working on a file you downloaded via your browser. For example, with Firefox on Windows, if you click on a file and instead of Saving it you Open with some application, it's downloaded as read-only.

That's true - but in this case it's a fully self created document 🙂

I'm not asking them to comment on future developments .... I'm asking them to implement this feature - no comment required.
And btw: current betas mostly seem to get bugfixes (what is very good!) - very little new (side) features. So I guess I'm not the only one desperately waiting for those essential improvements in the next (paid) major release that are due for many years now .... I'm sure there must be a second hidden beta program for the chosen to test these overdue features *bg*