Hangman

The improvement to the application of dashed strokes is beyond brilliant, it may only be a small change but it is hugely welcome, definitely looking forward to the addition of non-integer value adjustments in a future release but even the simple drag action for setting dash and gap intervals makes this feature so much more intuitive and dramatically improves the workflow for dashed lines and finally allows us to create professional layouts using dashed lines where before, well, you really just couldn't, thank you... 👏

Great, I had totally missed this feature!

Though you can deselect stroke and other attributes of the source object in the context toolbar leaving just fill as the selected option to copy...

Okay, so I think I figured it out...
I assume in point 4 you aren't physically selecting the preset again in the New Document window but just keeping any settings from the previous session because you're using the same preset. In that instance then both the New Document and Document Setup windows are independently sticky and replicate what you are seeing.
I'd assumed intially when you'd reached Point 4 that you were physically selecting the preset again by clicking it's icon in the list of presets which is what I've been doing and off course subsequently that results in the margins defaulting to Unlinked in both the New Document and Document Setup windows in Point 5.
If at Point 4 you are simply going File > New and then clicking Create in the New Document window without clicking the Letter preset in the left column then New Document and Document Setup act independently of each other and remain sticky between sessions.
Bleed however, as mentioned previously isn't sticky, as in it is always Linked in the Document Setup window regardless of whether it's Unlinked in the New Document window, so if anything I'd say that behaviour is perhaps incorrect.

I see the same issue, it affects all single pages in a document containing an even numbered of pages, e.g., the first right hand facing page and the last left hand facing page in a four page document.
We also still have the issue where changing the dpi isn't remembered when using the tab key as it should be though it is remembered when using the enter key.

I believe Affinity software uses the PDFlib 9.3.1 library... This is what the PDFlib 9.3.1 spec says regarding Variable fonts which is the same as the PDFlib 10.0 spec...
They are not supported in the current Beta and as far as I'm aware there have been no announcements from Serif regarding future support though it is obviously something that has been requested numerous times in the forums, however you also need to be aware, as you've rightly surmised, that the PDF specification itself doesn't support variable fonts... this is from Dov Isaacs a former Adobe Principal Scientist a couple of years ago and as far as I'm aware this is still the current situation unless anything has changed in the intervening years...

Exactly that, basically what InDesign and other software has to do is to convert the variable font to a legacy format or generate a static instance of each variable and bearing in mind that the Affinity suite uses the PDFlib 9.3.1 library to generate pdf files and variable fonts are not currently supported in the PDFlib library, I don't think we'll see support any time soon...
To be any use in a traditional print workflow I think first we would first need to see full support in the PDF spec, which as far as I know isn't there even in PDF 2.0 or PDF/X-6 (though things may have progressed, but I really don't know) followed by support in PDFlib library for Serfif to be able to support variable fonts in any meaningful way.

Hi @Chris B,
The issue relates to the zoom level, I see the same thing as @nwhit... as soon as you zoom in you should see the preview but when it's around 5% or less it doesn't preview at all you just see the checkerboard...
The other issue which has yet to be fixed is the ability to Alt Scroll to zoom for all vector formats which has been partically picked up here...
Alt Scroll to zoom works correctly for raster based formats but you can only currently use Cmd + and Cmd - for vector formats, I'm not sure if that needs adding to the same bug report...

PDF Preview.mp4

Hi @MarcBPL and welcome to the forums,
You need to ensure you have the static versions of Open Sans installed rather than the variable font version as variable fonts are not currently supported.
I just uninstalled the variable version of Open Sans and replaced it with the static version and everything then exports correctly using the correct font weights.

Hi @MarcBPL and welcome to the forums,
You need to ensure you have the static versions of Open Sans installed rather than the variable font version as variable fonts are not currently supported.
I just uninstalled the variable version of Open Sans and replaced it with the static version and everything then exports correctly using the correct font weights.

@Ash, It would be incredibly useful and a massive time saver if this also applied to vector selections, e.g., draw an ellipse or select a group of vector layers, select the crop tool and the crop will now initiate to be a min fit around the selection...
Use Case
On a daily basis I have a project that involves making lots of screengrabs which then require cropping in Photo prior to copying and pasting as a clipped layer in Designer. The crop is alway circular (or roughly circular) and quite often the item to be cropped isn't central on the screengrab so the current process involves drawing a circular ellipse with the ellipse tool in Photo, positioning the ellipse over the circular element to be cropped, expanding the size of the positioned ellipse to add a border to the crop (this allows for a little flexibility of movement when clipped in Designer in case the crop isn't perfect) dragging guides to the four edges of my circular shape's bounding box so I can then use the crop tool to snap to those guides prior to initiating the actual crop...
Having the ability to simply drag an ellipse using the ellipse tool to the size required, and then have the crop tool auto crop to the bounding box of the selection would save so much time...
It would be an added bonus if in doing so with a vector selection there was also an option in the context toolbar which allowed for a crop offset, both positive and negative, so you position you vector shape or make your vector shape selection and then enter a setting in the context toolbar, e.g., 5mm, 20px or whatever, based on the units of your document, so that when you select the crop tool it crops as a min fit around the selection + or - the value set in the context toolbar, that would then remove the additional step of needing to expand the size of the ellipse (in the example above) after positioning it to add the additional border prior to cropping the image...
While this may be a relatively unique case scenario I could see it being extremely useful in many other situations...

Hi Hangman,

It was actually Gabe who created the file, so I asked him and he said the blue box was placed exceeding the bleed area and was used to ensure that area was to be clipped to the bleed bounds and not visible outside it, so it does have a purpose. The PDF just crops the entire thing to the bleed area so that is working as intended.

I noticed in your revised PDF that you only included 1 page, and not all 5 - it is actually this reason that it displays correctly. If you have a PDF with bleed set, that contains more than 1 page, that is where it is going wrong. 

I've created a brand new 2 page doc in Publisher with 15mm bleed. Red rectangle extends to the bleed, and a green one inside the page. If I export a single page with bleed it displays correct when placed in Designer. If I export all pages and place it displays incorrectly.

I will get this logged  
2PageDocBleed_1Page.pdf 2PageDocBleed_AllPage.pdf 2PageDocBleed.afpub

It is, but only if you use the Delete keyboard key with the artboard layer selected. If you right-click on the artboard layer in the Layers panel & choose Delete from the popup menu, you do not get the Keep objects option & everything in the artboard is deleted along with the artboard layer.
I assume it is a bug, but it has been like that for forever, as far back as I can remember with the V1 version.

So a quick update, this happens across all apps and all versions including V1 but only when the Lock Colourspace padlock is unlocked. I've updated the original post to reflect this but would be interested to see whether others can now replicate this...

RGB Hex Crash.mp4

Interestingly not an option given on Mac. If your objects are nested in the artboard, which they are by default, then deleting the artboard does just that, it deletes the artboard together with its nested content without the Keep Objects option.
If you first drag the objects so they are no longer nested then deleting the artboard will again delete but maintain the objects...

Thanks so much. Problem solved!

Hi Hangman,

Thanks for letting us know. I can reproduce this here and will get it logged. As you say it only does it when Lock Colourspace is disabled.

Hi @DWALKER and welcome to the forums,
Although Symbol is recognised as being the font used, font manager suggests that some unsupported characters are used in the document... It appears to be unhappy with the mathematical symbols used for some reason, parentheses, commas and equals signs...
I think the issue is that Affinity is seeing the font as being the version of Symbol built in to the OS rather than the version actually used in the document...

You are correct, there are some inconsistencies in behaviour here with arrow keys and Magic Mouse. Have to be honest it's unlikely we'll clear all these up for 2.1 release, but will definitely put a mini focus for 2.2 of tidying all these up - will create a dedicated thread for any mouse scroll / arrow key / label click/drag, etc. field adjustment issues to be reported and we'll get them knocked out.

The improvement to the application of dashed strokes is beyond brilliant, it may only be a small change but it is hugely welcome, definitely looking forward to the addition of non-integer value adjustments in a future release but even the simple drag action for setting dash and gap intervals makes this feature so much more intuitive and dramatically improves the workflow for dashed lines and finally allows us to create professional layouts using dashed lines where before, well, you really just couldn't, thank you... 👏

Hi @JeremyHullah and welcome to the forums...
Once you create your path, set the stroke to none prior to adding your text and that should then work as expected...
I'm unsure whether or not this is actually a bug because in Affinity Designer as soon as you add text to a path the stoke is set to None and is therefore hidden but that's not the case in Publisher where the stroke remains visible.
The same behaviour appears in V1 and V2 so it may be by design but the difference in behaviour between the two apps seems strange.

It is not a bug. Publisher intentionally works differently from Designer and Photo, because only Publisher has the Text Frame panel. And the Text Frame panel is where you would control the visibility of the Stroke.

The improvement to the application of dashed strokes is beyond brilliant, it may only be a small change but it is hugely welcome, definitely looking forward to the addition of non-integer value adjustments in a future release but even the simple drag action for setting dash and gap intervals makes this feature so much more intuitive and dramatically improves the workflow for dashed lines and finally allows us to create professional layouts using dashed lines where before, well, you really just couldn't, thank you... 👏

I found a walk around thanks to @walt.farrell's guidance!
See link bellow @Hangman
 
 
Now, I found a way not to have to relink the PDFs after updating them in bulk. Still a pain to need to modify the DPI on all  linked PDFs.
 
Josue.
 
 

Thanks for taking the time to post, Hangman.