fde101

So...  what do you suggest?
 
Maybe...
 
Hmm, after reading that... maybe I missed my calling and I should go into marketing?

I think it would be more useful to have a Story Word Count, where a ‘story’ is a set of linked text frames. If the selected frame weren’t linked to any others, the result would be a Frame Word Count.

So...  what do you suggest?
 
Maybe...
 
Hmm, after reading that... maybe I missed my calling and I should go into marketing?

So...  what do you suggest?
 
Maybe...
 
Hmm, after reading that... maybe I missed my calling and I should go into marketing?

Good I read this: doing a backup of the original Cat ASAP.
Best regards!

It is not 100% clear from what I am finding in the guidelines, but what is clear is that any given window or app is not required to support full screen mode - in fact the guidelines actively discourage supporting full screen mode unless it makes sense to do so (something that a user will want to focus in on).
My interpretation is that the zoom button should work the way it does if full screen mode is supported by the window, and revert to the traditional zoom behavior if it does not.  In that interpretation the apps are working correctly.
However, I do seriously wish that there were a system-wide setting in the OS to reverse this behavior, zooming by default and going to full-screen mode only when option is held down.  For my own personal workstation it is not a big deal, but in a shared system being used to present content in front of people, going full-screen with a window can in some configurations black out other screens, including a projector, making it quite distracting and interrupt the presentation if a user hits the zoom button either accidentally or without realizing that it will behave that way.

So you like it when people break the rules only to fail to accomplish anything?
This thread actually manages to break all four of them (the first three by the OP and the last one by two of you):
https://forum.affinity.serif.com/index.php?/forum/52-feature-requests-suggestions/

This is really more of a CAD feature so not entirely within scope of an illustration program - I wouldn't expect it to have a particularly high priority right now, but it certainly wouldn't be an unwelcome enhancement.

It definitely has.  There is a reason that professional UIs are predominantly neutral gray: it reduces how much the color throws off your perception of the colors in the actual document.
Professional colorists working on video projects for major broadcast networks may need to work in rooms with walls that are painted using a very expensive pigment-free neutral gray paint so that the light (coming from carefully designed fixtures/bulbs) reflecting off those walls does not get tinted before hitting the display that they are using to judge their color choices.  While many of us won't be taking things to quite that extreme, having too much color in the surrounding UI is a rather obvious thing that can be avoided without significant cost in order to reduce bad influence on those decisions.  Shades of color/gray can also throw off your perception, so a relatively low contrast level is also desirable in a professional UI, at least to the point where it does not start to impact usability.

Thanks for the next beta.
I would suggest to add the Duplicate Link command to the contextual Layer menu as well.

For one thing, the ability to connect a single node in multiple places - for example, using one mask node as the mask for multiple other nodes, so that updating the mask in one place gets applied in several places.

Lately I've found myself wanting to select vector objects using a freehand (lasso) approach rather than the standard rectangle method. I've been using Vectoraster from LostMinds to create vector halftone 'sheets' that I can then bring into Affinity Designer to use within my compositions, often masked within an existing shape. This works really well, but it often means I have LOTS of unnecessary objects within my Affinity Designer file (many of them are often masked) which can lead to performance issues. I've taken to removing much of the unused area of these halftone 'sheets' to improve performance, but it's a tedious process. The only way to select them is with a rectangular selection, but often the shapes are curved and and be quite intricate which means having to go in and carefully remove only a few at a time in order not to accidentally remove ones that are actually visible within the composition.
Essentially, I'd like a way to select vector objects in a freehand manner this is similar to the way we currently are able to freehand select (lasso) a non-rectangular area of pixels.

The same one I do, apparently.
 
There are plenty of use cases for Publisher which do not require footnotes.  The publishing industry is not limited to the creation of books and scholarly works.
 
Consider just for starters:
Calendars Advertisements Church bulletins Product brochures (some have footnotes, many do not) Most works of fiction that I have seen do not have footnotes  
This is not a publishing task but a font management task best suited to a dedicated application.
 
This is hopefully a temporary situation.  Printers should not need InDesign files - they should only need the PDFs, which Publisher already does.
 
I'm assuming by this that you are looking for a plugin or scripting API?  That is currently missing but is being discussed already on another thread.  It is not relevant to many users who are working solo/independent or in a smaller business (as opposed to corporate) setting.

I don't think you will get it down to "none" without losing functionality as the thumbnail is used as a drop target when rearranging layers to indicate that it should be a mask instead of a normal child.  Instead it may be that the thumbnail could be the same height as the text if that is all you need to have it present for.

The first is in current 1.9 beta cycle

There are existing discussion  threads for both of these topics.
JET

The stock panel is nice but I often face difficulty judging the photo in smaller size. 

For one thing, the ability to connect a single node in multiple places - for example, using one mask node as the mask for multiple other nodes, so that updating the mask in one place gets applied in several places.

https://forum.affinity.serif.com/index.php?/forum/52-feature-requests-suggestions/

Whoever is doing that is violating forum guidelines:
https://forum.affinity.serif.com/index.php?/forum/52-feature-requests-suggestions/

You an kind of work around this using artboards:
Select the artboard tool, set the popup on the context toolbar to "Selection" and click "Insert Artboard".
That will give you an artboard perfectly matched to the selection.

This runs contrary to the design of the application.  Affinity Photo is by nature a destructive photo editor.  It does have some non-destructive capabilities, and extending this to some degree into the Develop persona has been discussed in other threads (suggest searching for and adding your comments to the existing thread if you have something to add), but the program as a whole will never be 100% non-destructive.
 
This can bloat file sizes, particularly for larger and more complex projects.  I think there should be a preference as to whether or not this should be enabled by default for new documents, as some will want it and others will not, depending on how they work.
 
Other people are complaining that it doesn't really crop, but want it to destructively crop the canvas when they use it.  This again is a function of different people working in different ways, and the current crop tool is likely most appropriate for Affinity Photo.  You can still use a shape as a mask to gain the effect of cropping an individual layer.
Also, the concept of cropping a layer is kind of foreign to the develop persona anyway as it only ever operates on a single layer.
 
Wrong tool for the job.  This feature is not ordinarily needed in a photo editor and is a very reasonable feature to have left out to help differentiate the products.
If you have both applications and you really want that capability, you should be able to bring a "vector layer" (not really what they are but whatever) from Designer (or Publisher) into Photo and store it as an asset so that you can drop it onto other documents later on.

As the Affinity series apps primary target professional users and those who aspire to be such, this seems entirely appropriate.
 
Just about anything that is worthwhile for pros is going to seem complicated to a "noob" - the secret is to take the time to learn.
 
 
That said, this request amounts to "make it easier" - but there is no specific indication of specifically what it is that you currently find to be difficult / unintuitive...  can you be more specific about what it is that you are having trouble with?

One complication is that both control and command already have assigned functions for this tool.  There are no modifiers left to use for this.
However, as the function assigned to the command key only has an effect when the user drags from within the selection, it could be made to do this when the mouse is not over an existing selection when starting the drag, and retain its current behavior when the mouse is over an existing selection.
This might still leave Windows users out in the cold, as the same could not be done as readily with the current control key behavior...  I'm not sure how things are mapped on Windows so not sure how this would align with what is currently in use there.