Hangman

Regular duplication of symbols keeps the symbol status of the group, so I would consider this a bug as well.

I agree, to me this appears to be a bug as I can't see any logical reason why one of the three symbols correctly moves/duplicates but the other two don't.
Hopefully, someone from the moderation team can confirm and log if appropriate.

I assume you mean “Fit” view to window (as in Cmd-0), but this behavior occurs irrespective of the number of documents that are open. If you look at the first version of my Tower of London photo, you’ll see that it is the only open document. Also, I almost never use the standard versions of the filters, destructive little beasts that they are, and even when I have to do so, certainly don’t leave them open and just sitting there, unapplied. So, that can’t explain my dilemma.

I agree, to me this appears to be a bug as I can't see any logical reason why one of the three symbols correctly moves/duplicates but the other two don't.
Hopefully, someone from the moderation team can confirm and log if appropriate.

Good info - thanks for that, Hangman. I'll try your PDF test myself using the 2.2 suite and see if the bug still exists.

Oh I didn't notice that, thanks.

Thanks Hangman. I think this is what is happening. When creating the 2 files, I started with 2 different PDF files and it seems they are quite different sizes. Once I resize to the same dimensions and resolutions, my line width issue resolves itself. 

Hi @bcposi,
What is the resolution of the document you used when initially creating your Style and what is the resolution of the document where you are then applying your style...
If the document resolution when creating the style = 400 dpi and the document resolution when applying the style = 72 dpi
Stroke width factor between document resolutions = 400 / 72 = 5.56 Applying the stroke width factor to a 10 pt stroke = 5.56 x 10 pt = 55.6 pt  

I guess it's effectively the same thing but it also happens when adjusting the line between Opacity values when using the Transparency tool.

Just a quick update for this thread.  I've today found another way to trigger this bug in Affinity without using the Scroll bars.  Place a shape on the page and from the Context toolbar select Fill>Gradient and now move the line between the gradient points and your bounding box will disappear and won't come back unless you zoom in and out.  
I've added this information to the report  

I agree, to me this appears to be a bug as I can't see any logical reason why one of the three symbols correctly moves/duplicates but the other two don't.
Hopefully, someone from the moderation team can confirm and log if appropriate.

Also, in case it's relevant, JPEGQualityEstimate appears to be a tag/value calculated by ExifTool, not an actual value embedded by the application that produced the file. It's documented by ExifTool as an estimate of the IJG JPEG quality setting for the image, calculated from the quantization tables.
That would make sense, as the forum is probably implemented using PHP software and functions, which would be involved in saving and converting uploaded attachments.

Thank you.
By the way, when I tried clicking and dragging the color picker over a page, Publisher suddenly appeared in the System Preferences/Security & Privacy. I've now checked it.

I switched off hardware acceleration without any change. I suspect M1/Sonoma, as well... 
It does not have to do anything with the flickering, I can confirm that. We'll see, then.

Another simple alternative is to put the Pixel layer inside a Rectangle layer (with the same size and position as the Pixel Layer) and give the rectangle a stroke as required – see attached image. (The Rectangle layer then becomes the vector container, as mentioned by Dan C above, which the initially placed image had.)

Welcome to the Affinity Forums @UltraDev 
I can confirm that this is expected behaviour - a placed 'Image' or 'Document' layer is rendered within a vector container, therefore can have Stroke settings applied.
Once you rasterise the layer to a 'Pixel' object, it is no longer contained within a vector container and therefore the Stoke attributes simply aren't' compatible with this layer type.
As mentioned above, the Select menu options are related to an active Pixel Selection ('marching ants') on your canvas and are completely separate from the FX options, which do not require an active selection.
Unfortunately as confirmed by Return, there is currently no 'trace' tool within Affinity apps - though this is a highly requested feature and one our team hope to implement in a future update.
You may be interested in the following list of third party alternatives for 'tracing' bitmaps/selections to vector objects:  
Sorry to hear you're experiencing rendering errors in Affinity, this isn't something we're seeing reported from other users consistently, therefore it may be related your system, Affinity document etc.
Firstly, if you experience rendering errors then please try zooming in and out of the document - this will force the canvas to redraw & refresh and should hopefully mean you no longer need to close and reopen the app.
Secondly, please ensure that your GPU driver is fully up to date, directly from the manufacturers website, as outdated GPU drivers can cause rendering issues within Affinity apps.
I hope this helps!

Well, I was working on a text and changed the font "Reem-kufi-fun" from Google,
Affinity designer frizz, I need to force quit and restart, them impossible to relaunch, stop on initiating panel.
Lucky, I wrote the name of the font before force quite Designer, and I can deactivate this font, then try again, and it looks working now.
So, actually, it's not a network problem, it's a front problem
Voilà

HI Hangman,
I"m glad too. I'll report any new crashes if any occur, but hopefully they will not. At least I now know how to look for extraneous things within a master.
Thank you again for your help.

Hi @walt.farrell, @MikeTO beat me to it as I was replying to your question...

It's not the document tabs that throw off the calculation but the rulers. I've reported this before.
Solution - turn off the rulers. 🙂
 

Books use absolute paths to their chapters. FYI
 

Hi @Mr Lucky,
Unless this is a new issue specific to Ventura then this is a long outstanding bug. The official position from Serif is that Vector file formats are non-zoomable (even though they actually are and I seriously hope they don't fix that) but Raster file formats are zoomable...
The bug on macOS is that when selecting an export format if any text entry field has focus, which it does by default for most formats, this overrides any attempts to zoom using the keyboard shortcuts so with something like a PDF export you need to first select and non-editable field in the export options panel, e.g., clicking the 'Include Layers' option so that non of the editable text fields have focus. At that point, the default keyboard shortcuts will work, Cmd +/-, Cmd 1, Cmd 2, Cmd 3 and Cmd 4.
The same issue applies to Raster formats, again you need to ensure none of the text entry fields have focus (e.g., selecting JPEG results in the Width field having focus) to be able to use the keyboard shortcuts but Raster formats do allow you to Alt mouse scroll over the preview in addition to the keyboard shortcuts for zooming...
Note: I'm showing Monterey here where the above is working albeit haphazardly so you may not see the same on Ventura if this is a genuine bug.

Export Preview Zoom.mp4

Like you say, just another of those Windows/macOS differences I guess.
Hopefully your original issue gets some attention from the developers when they have time.

I think you might be right.
I tried creating a simple non-facing document with 5 pages of 3”x3” and I saw no zoom changes.
However, I created a different non-facing document with 5 pages of A4 Portrait and the zoom changed from 73% (after pressing the “Last Spread” button) to 71% after double-clicking the last page in the Pages Panel, but was unable to replicate it after that (the slight shift in position is still there though).
The 'zoom thing' might be a 'red herring'.

Hi @DoctorBe,
ExifTool correlates with the JPEG Quality Settings in Affinity Photo...
Exiftool -JPEGQualityEstimate filename.jpg
Processed RAW file exported as JPEG from Affinity Photo using Quality Settings of 100, 80 and 50