R C-R

My calculator says the inverse of 1.15 is approximately 0.8695652174, so depending on the internal precision of the app & the number of steps applied, it is possible stepping up & then down may not ever return the size to exactly its original value.  

I know about the blue outline. But at least on my system, getting it to appear by clicking on a field label often does not work, & sometimes even when it does a different field is selected than the one whose label I click on.
 
I know one of the reasons it sometimes doesn't work in the Studio panels: often when I move the mouse pointer from the workspace into the Studio area, the pointer changes to the double arrow with a vertical line through it (the one used to resize the width of the Studio) & remains 'stuck' in that mode. This occurs most often when I initially move the pointer into an empty space in one of the panels but it also happens frequently when I move the pointer directly into the Transform panel.
 
With the pointer in that mode, clicking on the field label has no effect, but clicking on the field itself does give me the blinking text cursor somewhere in the field's current value. Once I have done that, the pointer reverts to the normal pointer arrow if I move it & I can successfully click on a field label to select all of its contents.
 
Clicking on the field label also does not work correctly in the Studio Color panel when the labels are the one character values for sliders (like R, G, & B or C, M, Y, & K) although strangely it does (usually) in the color dropdown in the Context toolbar. Weirdly, in the Studio panel clicking on any of those one character field labels does not create a blue outline or highlight the field value but typing any number after doing that changes the "global opacity" of the document, according to the Edit menu Undo text or History panel.
 
There are some other anomalies I have not yet completely sorted out, like the click zone for the field label not lining up with the characters of the label or apparently selecting a different field than the expected one. I am not certain what causes this or how to reproduce it reliably, but some of it may have something to do with the OS X System Preferences > Accessibility settings I use. I know the "Increase Contrast" setting (which I use) causes the triangles in the disclosure buttons on the Layers panel to go dark instead of being the same light color as the circle that surrounds them, a confirmed bug I reported long ago, but I have no idea if that contributes  to the label problems I see.

@Pindasmeer
 
I don't have a link handy to refer you to but in the past one of the Affinity staff said there were 'some problems' with offering the Windows apps through the Windows App Store that they wanted to avoid, which is why they decided to offer them through their own store. I do not remember if there was any mention of the specific nature of those problems or if so what they are, but they did consider that.

@Pindasmeer
 
I don't have a link handy to refer you to but in the past one of the Affinity staff said there were 'some problems' with offering the Windows apps through the Windows App Store that they wanted to avoid, which is why they decided to offer them through their own store. I do not remember if there was any mention of the specific nature of those problems or if so what they are, but they did consider that.

1. Save with history, snapshots, & any other Affinity feature not supported by the JPEG format won't matter if you save the file as a JPEG, however you save it to that format. JPEGs will always be flattened into a single pixel layer because that is all the format can support.
 
2. If the original JPEG includes no color profile, opening it in Affinity will assign whatever profile is set as the default in Preferences > Color Profiles for file's color space. This will add to the file's size when saved back to a flattened JPEG. The added size will vary depending on the size of the color profile, but typically it is not more than a hundred KB or so.
 
3. JPEG uses lossy compression to reduce image file size. It is less effective on images with lots of fine detail (like complex textures, sharp edge transitions, etc.) so if your edits add more detail than was present in the the original, file size will increase, sometimes substantially. Without resorting to exporting to JPEG format, you can reduce file size when saving flattened by eliminating unimportant details, often enough that the file will be smaller than the original.
 
For example, a photo that includes a lot of clear blue sky might actually have hundreds of slightly different shades of blue in different areas of the sky. Painting over them with a brush set to a blue shade that is the average of the blues in that area will make the compression much more effective. Using a denoise filter can also be very effective for this.

If I understand what the developers have said in the past about this correctly, they use the GUI provided by the OS as much as possible. The core code was developed from the beginning to be platform independent to make it easier to offer both OS X & Windows versions, & an iOS version in the near future.

In case it isn't obvious, you can create the slices in the Export Persona Layers tab by selecting the layers (or groups) in that tab & clicking the "Create Slice" button at the bottom of the panel. Then switch to the Slices tab & click the "Export Slices" button to export each layer (or group) to a separate file.

Probably the same as with any other software that goes through the usual release lifecycle.
 
Just because the sneak peak shows the app working in a controlled environment on one iPad Pro model, using an Apple Pencil for input, does not mean it will work with non-pro iPads, or when using something other than the Pencil for input, or is stable & bug-free enough for a public beta, much less to be a release candidate.

Based on my experiences in other forums that have a points/rewards system, I am not in favor of one here. The reason is this tends to promote competition among some users, which leads to disputes & bad feelings about who should get credit for posting first, whose post best explains the issue, etc.

Yikes... Adding a knife tool to AD seems to be the solution.

This topic, & in particular this comment & several of the posts by A_B_C, got me thinking: what exactly is a spiral, & how could I make a "true" one? This very quickly led me to the Wikipedia Spiral article, where I was reminded of something I was previously only dimly aware of; that being there are a lot of different kinds of 2 dimensional spirals.
 
If I am not mistaken, all the techniques mentioned here produce Fibonacci spirals. Wikipedia tells me they are approximations of the Golden spiral, which is one of the many continuously expanding true spirals.
 
At this point I realized something: a true spiral (one with a continuous "growth factor") would require infinitely many Bézier nodes; otherwise it would be a stepped approximation, right? If that is indeed true, there is no way Affinity could provide a true Spiral shape tool (& it makes me wonder how other apps with that tool handle this).
 
Anyway, I started thinking about ways to create "truer" spirals in Affinity & I have an idea about that I want to hear what you think of.
 
The basic idea is to create a two node line, set its center of rotation to one end, duplicate it, slightly rotate & lengthen the dup, then power duplicate that a bunch of times. The nodes opposite the center of rotation look to me like nodes on an Archimedean spiral, so by snapping a new line drawn with the Pen tool to each of those nodes in turn, this produces something resembling a stepwise approximation of that kind of spiral.
 
To make what I am talking about a little clearer, I have attached an afdesign file (in 1.5 format), with the history included so you can step backwards to see what I did. I only extended the new line through about one turn of the spiral -- it is a tedious process, but I hope this gives you an idea of the procedure.
Archimedean Spiral?.afdesign

You can open those hand edited SVG files in any of your browsers, in order to see how things should usually look.
<?xml version="1.0"?> <svg width="120" height="120" viewBox="0 0 120 120"     xmlns="http://www.w3.org/2000/svg" version="1.1">   <defs>     <marker id="Triangle" viewBox="0 0 10 10" refX="1" refY="5"         markerWidth="6" markerHeight="6" orient="auto">       <path d="M 0 0 L 10 5 L 0 10 z" />     </marker>   </defs>  <polyline points="10,90 50,80 90,20" fill="none" stroke="black"       stroke-width="2" marker-end="url(#Triangle)" /> </svg> Yes it seems AD doesn't parse or can't interpret SVG <defs> and <marker> elements. That's a pity since every browser usually can do and it would be useful to have, probably also for writing then back (exporting) by AD internally own used and defined arrowheads and polymarkers styles into the SVG format.

I think you will find that the support offered through these forums from the Affinity staff (& to only a slightly lesser extent from other users) is amazingly good, among the best available for any software of any kind. Most posts get replies within a few hours, often with detailed explanations for anything that might not be obvious to new (& sometimes not-so-new) users.
 
It is a good idea to refer to the built-in help, the tutorial videos, or search the forums for similar topics before posting, but since that isn't always practical, do not hesitate to post any questions you have. Chances are excellent that at least one person if not several will be more than happy to take the time to help you with anything that isn't clear to you.  :)

No screenshot! Fixed.
 
The EXIF Studio panel is also available in the Photo Persona. Add it from the View > Studio submenu.

The DPI setting is relevant only to the physical dimensions of printed output, or when you export to a raster format like PNG or a rasterized PDF. Watching the Affinity Photo - Understanding DPI video tutorial may help you understand when DPI is important & when it isn't.

When you select an artboard containing text with the Move tool, you should see an extra control handle outside the eight around the edges of the selection box, located below & to the right of the lower corner of the box. Using this handle to resize the artboard should scale all the text proportionally.
 
Unfortunately, this handle has no equivalent in the Transform panel so you have to do it by dragging in the workspace. 

No screenshot! Fixed.
 
The EXIF Studio panel is also available in the Photo Persona. Add it from the View > Studio submenu.

Indeed who cares, if somebody is switching over into the one or other direction here. Everybody has finally to choose for themself, what they are personally and individual comfortable and most productive with, for what ever reasons!

Based on my experiences in other forums that have a points/rewards system, I am not in favor of one here. The reason is this tends to promote competition among some users, which leads to disputes & bad feelings about who should get credit for posting first, whose post best explains the issue, etc.

When i close an Affinity document, either Photo or Designer, if there have been changes, it prompts if I want to save it. That's fine and expected, but then after saving, it doesn't close, I have to select "Close" again. Seems to me the expected behavior would be to Ask - Save - then it would Close.
Is this the way it should be? Does anyone else think the way I do on this? Not a big thing, but it seems counter-intuitive to tell it to Close twice.
 
Cheers – Timber

I am not sure you understand what I suggested, which is not using the slice tool but instead using the Layers tab in the Export Persona to create slices (using the "Create Slice" button at the bottom of the panel) to create slices from the layers or groups in your document, then switching to the Slices tab to do the actual exporting.
 
This will not export everything in the mockup in the slices created this way, just whatever is in each layer or group individually.

Based on my experiences in other forums that have a points/rewards system, I am not in favor of one here. The reason is this tends to promote competition among some users, which leads to disputes & bad feelings about who should get credit for posting first, whose post best explains the issue, etc.

Based on my experiences in other forums that have a points/rewards system, I am not in favor of one here. The reason is this tends to promote competition among some users, which leads to disputes & bad feelings about who should get credit for posting first, whose post best explains the issue, etc.

Because they share common properties and common processes - that makes Affinity apps great to use (and greater still when Publisher is launched).

As that post makes clear, prior to around 1986, graphic designers had to work sans-Serif.  :lol: