fde101

Maybe the popup could be enhanced to include a button that opens the Font Manager?

Hi A_B_C,
A Picture Frame can act as a parent clip object for any number of child objects just like any other Affinity object. In the case of Picture Frames though, one, and only one of those children can be flagged as the ‘content’ (this child object is indicated in Layers by the box with the diagonal cross in it). The object marked as content will scale according to the Picture Frame properties, the others will scale like child objects generally do, and in fact regular constraints can be applied to them. This allows you to, for example set up a frame with adornments, or maybe some kind of watermark.
To add an object as a regular child you can drop it in the layers panel in the bottom third or so of the target parent. You can add as many children as you wish in this way. To add it as content you can drop it, again in the layers panel, in the centre, vertically of the parent. The object will obey the Picture Frame fitting rules and by default will be scaled to max fit the frame. If a child flagged as content already exists it will be replaced. This is equivalent to choosing ‘Replace Image’.
So in your case, in the first instance when you created your picture frame we have chosen not to automatically make any existing children the content object. In fact, if we did, aside from the potential problem of choosing which child should become content, this would typically result in the child being scaled to fit the frame as it would have to obey the fitting rules. So, as the frame still has no special content object it is drawn with a diagonal cross. Then, in your second case, as populating the frame will only ever replace the content object and there isn’t one, the regular child is not removed and the content object is added.

Thanks alang i shall get this logged for development to look into

Sorted (and this is Beta - thank you). And those shortcuts are the same as the other program I use!

Hi,
I was just working in a document using the text box tool. Not the artistic text, but the other text frame function. When I went to decrease the size of my text box so that it fits the type perfectly, I double clicked the horizontal arrow on the outside of the text box. That worked. I then double clicked the vertical (down) arrow. That made the text align itself completely vertically, so I hit command z and tried it again (I wasn't sure if I hit something else the first time). On that second time of double clicking the text box's down arrow, my affinity publisher froze. I had to force quit. Replayed the same exact scenario with the same outcome. Assuming it's a bug? Figured I would bring it to your radar.
Thanks!
Rachel

I would say it is Dark Mode being wrongly applied by Affinity Publisher (and probably the other edge cases I have heard or). But most importantly Why are we reading the EULA?

The problem relates to a master page command in combination with the document using Save history with document. We are looking at the problem and it was unknown so STILL EXISTS in the current beta. We have managed to recover your document and you will find it here
Link removed
When you load your document back into Publisher please can you turn off "Save History with Document" or this could happen again. Our advice to all beta testers is now not to use "Save History with Document" in Publisher beta while this master page issue remains unresolved.

@Bob Grahame You can get utilities that will do this for you on the fly, temporarily displaying them as an overlay on your screen.  I'm on a Mac and recently/finally bought Ergonis' KeyCue.  Here's an example showing my current shortcuts in beta 1.7.0.145.  Note that this includes a few that I have defined myself and should not be regarded as the default set.  Note also that what KeyCue displays is interactive, not just a static graphic that you see here.
Still on Macs, there is at least one other utility that you could try which is free: CheatSheet, from Media Atelier.
I'd be surprised if there wasn't something similar available for Windows users.

I believe that control is to zoom the navigator itself, so why would you place it outside of the navigator interface?

Still experimenting with AP - Can I suggest you move the zoom tool from the 'Navigator' tab to the unused bottom border (see attached). This could apply to both Publisher and Affinity Photo. This would release the Navigator tab for other tasks as well as producing less clutter.
zoom tool.pdf

I would expect and prefer the latter.

Hi Chris26,
The confusion comes form the two "types" of raster layers we have in the program. You can identify the type of layer looking at the table between parenthesis after the layer's name in the Layers panel. The types are pixel layers and image layers. Image layers are a "special" layer type that retains all the original image data - you can think of them as embedded images -. They are created when you use the Place Image Tool (in Affinity Designer and Publisher only), the File ▸ Place command or when you simply drag them from the Finder (Mac) or File Explorer (Windows) to the canvas of an opened document. They can be transformed globally (rotated, skewed etc) without losing quality but they cannot be edited/manipulated at a pixel level. For that they must be rasterised first. To do it right-click on them in the Layers panel and select Rasterise. They are then converted to a pixel layer type which you can then manipulate at a pixel level. Image layers are rasterised using the DPI value set in the Document Setup dialog.
If you then decide to place them inside a picture frame (no matter the type of layer), use a shape to clip them or whatever functionality you may think of that's up to you.

We will have this capability soon, hopefully in the next build. As MEB says, you can already apply multiple masters to a page.

If you set one of the color nodes in a gradient using a global color swatch, it seems to copy out the color instead of referencing the global color.  As a result, if the global color is changed the gradient does not update.
It would be much better if the gradient updated along with other users of the global color swatch.

There is a minor problem with Tabbing though the fields, it doesn't wrap around, once at the end it exits. But hey, thanks for the major improvement.

I was hoping that we would be able to save them out as presets like Grids and Axis Manager. Maybe later. 

I am skeptical that this would take a "major" rewrite - maybe a minor one...  but that is ultimately for Serif to decide.
In any case, it would be a more correct level of functionality.

If you set one of the color nodes in a gradient using a global color swatch, it seems to copy out the color instead of referencing the global color.  As a result, if the global color is changed the gradient does not update.
It would be much better if the gradient updated along with other users of the global color swatch.

That's correct. We hope to put it on auto-update tomorrow but for now it is a manual download.

If you set one of the color nodes in a gradient using a global color swatch, it seems to copy out the color instead of referencing the global color.  As a result, if the global color is changed the gradient does not update.
It would be much better if the gradient updated along with other users of the global color swatch.

It's an even worse example considering that it is a text frame and you can turn on visible frames for those (Show Text Flow in the View menu).

Generally they shouldn't be mixed, because often the Typographic one will work for numbers like 2 and 3, but not for 5 or 6, so superscript 256 looks weird because the 2 doesn't match the other two numbers.

Even project leads deserve a week off now and then.... Yes sometime quite soon.

Maybe a menu command (allowing a shortcut to be assigned) that creates such a tab stop if it does not exist then tabs forward to it?