lepr

Use your partially transparent "vignette" layer as a mask on an Exposure Adjustment, and put the masked Exposure Adjustment as the topmost object inside the Layer (or Group) containing the pieces of frame. That will restrict the adjustment to just the content of the Layer (or Group).
FrameAnswer.afdesign
 

Correct I never release the mouse button in line mode I click then drag the line out with the mouse button held down, maybe because I am used to using the apple pencil on the iPad version and that is how I imitate what happens on the iPad version on the desktop.

There is yellow rectangle with Erase mode nested in the grey rectangle in Layer 2.

The expected behaviour:
If document units is pixels, changing PPI should not change the quantity of pixels, but the document's physical size should change.
If document units is physical (for example, inches or millimetres), changing PPI should not change the document's physical size, but the quantity of pixels should change.

From the app's help document:

When the shift key is depressed to constrain angle, the intersection-snapping for the second node is dependent on the mouse button being depressed while the pointer enters the vicinity of the desired intersection.
In my opinion, that dependency should not exist, but you can work with it: ensure both shift key and the mouse button are depressed as you move the pointer close to the required intersection, and only release the button to create the node when the snap is indicated.
(I think Paul was successful by pressing the mouse button to create the first node of a line and then not releasing the button until the snap was indicated for the second node.)

The expected behaviour:
If document units is pixels, changing PPI should not change the quantity of pixels, but the document's physical size should change.
If document units is physical (for example, inches or millimetres), changing PPI should not change the document's physical size, but the quantity of pixels should change.

Not on my computer or the computer of others in this thread.
APub2 (2.0.3 and 2.04 on macOS) is behaving correctly only when document units is pixels.
When units is physical, a change of PPI is wrongly resulting in a change of physical size because the quantity of pixels is not being changed, which is the behaviour expected (and correctly happening) when units is pixels.

The free bundle of content promised for our customers who have upgraded from V1 to V2 is now available. For more information and how to claim please see my latest announcement here.

Thanks,
Ash

Hi all,
Yesterday marked the end of our ‘40% off V2’ launch offer. With that offer ending I wanted to let you know about a couple of things:
Ongoing upgrade price for the Universal Licence
As I mentioned in my previous announcement (here), offering a specific upgrade price for V1 customers had many complications and is why we decided to run a launch offer in the way we did. However, we listened to the feedback we had around that, and have used this time to implement a method to offer an upgrade price long-term — allowing customers who have not upgraded yet an opportunity to still do so at a better price than a new customer.
All the issues I previously referenced around App Store conflict still exist, so the upgrade offer:
Is only available for purchases of the Universal Licence (offering upgrade pricing on individual apps just is not possible without conflicting with App Store guidelines as each individual app has their own App Store listing) Is only available for purchases made directly from our website (we cannot offer this upgrade discount for people purchasing via an App Store) The ongoing upgrade offer is 25% off the Universal Licence, and also includes a free content bundle (the Creative Collection) worth over £200. To claim this discount, we will validate you own V1 based on whether you previously purchased V1 from us directly, or have registered a V1 App Store purchase to your account. This offer is available from our new upgrade page.
Creative Collection content bundle now available to anyone who has already upgraded from V1 to V2 during the launch offer period
 If you already upgraded to V2 during the launch offer period, we also wanted to make sure you could retrospectively claim this new free content bundle.
We have worked hard to make this a valuable gift, and have tried to cover various different use cases of our apps. The bundle includes some high-quality fonts, brushes, LUTs, icon assets and resources and, as mentioned above, is worth over £200. So, if you have already purchased V2 and you previously owned V1, you can claim this content for free as a special thank you for your support (in addition to the 40% discount you would have already received on your V2 purchase during the launch offer).
To claim the Creative Collection, please visit our upgrade page and scroll down towards the bottom where there is a ‘CLAIM NOW’ link under ‘Already upgraded from V1 to V2? You can get the Creative Collection for free below’.
After following the link, you’ll be taken through the validation step of checking your account as being someone who owned V1 and has purchased V2. The way we confirm this is by seeing a V1 purchase tied to your account, whether you purchased it directly from us or you registered an App Store purchase to your Affinity account.
Claim your free content now
We understand there will be some of you who did purchase V1 from an App Store but may not have ever registered it to your account (and as you probably don’t have V1 installed anymore, no longer have the ability to register it). In that case we will need to try to validate that manually with you. So, please first try getting the Creative Collection using the link above and if that fails, drop us an email with your Affinity ID to affinity@serif.com (subject: “Free Content”) and we will do our best to help. If it’s possible for you to dig out your original App Store receipt for your V1 purchase, it will speed up the process if you include that in your email to us.
Other than that, thanks again for all your continued support. We hope you enjoy your gift!
Thanks,
Ash

Enable Transparent Background in the Colour tab of Document Setup to get a checkered background. (Also, an Artboard needs to have no opaque fill or the checkerboard will still be hidden.)
 

 

Apologies for the delayed response here all - I can confirm our team are aware of issues with Boolean operations on text objects converted to curves and our team are working to resolve this ASAP.
I will be sure to update our development log with this thread now and we offer our apologies for any inconveniences caused due to this in the meantime.
I hope this helps!

If the selected masked object is a Group (or Layer), an Export Selection Only is as large as the entire Group.
If the selected masked object is not a Group (or Layer), an Export Selection Only is just large enough to contain the masked region of the object.
That difference seems illogical to me, and I think the export should be the size of just the masked region in both cases. 
In other words, the output of Export Selection Only of a masked Group (or Layer) is wrong currently, in my opinion.

If the selected masked object is a Group (or Layer), an Export Selection Only is as large as the entire Group.
If the selected masked object is not a Group (or Layer), an Export Selection Only is just large enough to contain the masked region of the object.
That difference seems illogical to me, and I think the export should be the size of just the masked region in both cases. 
In other words, the output of Export Selection Only of a masked Group (or Layer) is wrong currently, in my opinion.

Yes, clearly there's more similarity between Smart Objects and Affinity embedded/linked documents than there is between Smart Objects and Affinity Image objects or between Smart Objects and Affinity Pixel objects.

the shortcut is the c key

Context is everything. 
An example would be like:
Sabon 12/14
Either directly beside example type, or an arrow pointing to example type.
While you might confuse such notation as a fraction, a person setting type, at least with some experience or explanation, would not be. 

12/14 is how type is still spec'd, in this case. It's taught that way still and is so used in every branding guide I've ever been sent. 
It's up to the user to understand that and how it applies to software. 

You kept calling it a fraction. It's not a fraction. That's all. 
Maybe consider the 12/14 a contraction. Or, maybe educate yourself. 

No Walt that is not what I said! I'll say it another way. 2pt leading is the same as saying 12pt on 14pt. That's the way we used to state 2pt leading.
As I understood it the font designer designed the font which included the space under the character which determined the minimum line spacing. Its up to the typographer if he wants add more line space. The old style lead fonts did not allow the removal of the minimum space between lines but DTP can let you overlap lines if you so desire! I can understand removing space from between lines of capital letters to make it look less gappy but not when its u/l case.

OK Walt I'll bear that in mind for the future.
With respect I'm the designer and not AD! I want what I want. My typography goes back way before DTP and it's complicated and too much choice way of tdoing things. Character, line and paragraph spacing was all done using leading. If you wanted 2pt line spacing it would have been referred to as 12pt on 14pt. Line lengths were measured using an 'M' rule. In fact this system was still used in the very early days of computer typesetting.
It was only when companies found that they could use the office secretary to type out their printed matter and sat then in front of a DTP computer. Skilled typographers were no longer needed! Once the secretary was able to understand all the different aspects of DTP then if the type didn't fit they just stretch it! If an image didn't fit then they just stretch it. That's graphic design went downhill!
Just sayin'.
I tried to Justify left but that didn't seem to work. When are you supposed to apply such a command, when you create a text box or when you type in it? Do you have to select the txt and apply it?
 

If rasterisation in an export is acceptable, then an Adjustment can be applied to the objects in a Group. For example an Exposure Adjustment with a mask to give it shape can produce an effect like a cast shadow. Here's a simple example with an editable vector mask on the Exposure Adjustment: Cast shadow.afdesign

Affinity could handle inherent mask identical to separate mask layers.
meaning offering „release mask“ that would create a seperate mask layer, and then fills the inherent. Saves a few clicks (select from layer, create mask, move mask layer, fill adjustment alpha)

The new Shape Builder Tool is ideal for jobs like this.
select all the objects (cmd+A) activate Shape Builder Tool (S) use the minus button in context toolbar to choose delete mode click on each of the unwanted triangular regions  



 

The new Shape Builder Tool is ideal for jobs like this.
select all the objects (cmd+A) activate Shape Builder Tool (S) use the minus button in context toolbar to choose delete mode click on each of the unwanted triangular regions