LJM

Feature Request 1: Consider allowing all applications in the Affinity Suit to link documents like Affinity Publisher.
Feature Request 2: If/when linking across all Affinity Applications is possible, consider allowing the user to select not only select a specific art board or the entire document but also any layer at any level in the layers hierarchy of a linked or embedded document.
Feature Request 3: Similar to linking, consider allowing for application-level symbols. Currently, symbols only exist at the document level. Such a feature achieves the same ends in feature requests 1 and 2 on the same computer.
—
For example, if a company creates a logo that is to be up to date in any subsequent work such as app and website UI mockups in Affinity Designer, print-like publications in Affinity Publisher, and photos in the editing stage in Affinity Photo, it would be great if feature request 3 is implemented to allow for an application-level symbol to hold that logo so that any changes to it synchronize across all other Affinity documents containing this application-level symbol. Extending the example to feature requests 1 and 2, if the company hosts the file on a server from which their designers’ computers can access it, they could simply link to it instead of embed it so that changes to the master logo file occur in real time to all Affinity documents that link to it.

Feature Request 1: Consider allowing all applications in the Affinity Suit to link documents like Affinity Publisher.
Feature Request 2: If/when linking across all Affinity Applications is possible, consider allowing the user to select not only select a specific art board or the entire document but also any layer at any level in the layers hierarchy of a linked or embedded document.
Feature Request 3: Similar to linking, consider allowing for application-level symbols. Currently, symbols only exist at the document level. Such a feature achieves the same ends in feature requests 1 and 2 on the same computer.
—
For example, if a company creates a logo that is to be up to date in any subsequent work such as app and website UI mockups in Affinity Designer, print-like publications in Affinity Publisher, and photos in the editing stage in Affinity Photo, it would be great if feature request 3 is implemented to allow for an application-level symbol to hold that logo so that any changes to it synchronize across all other Affinity documents containing this application-level symbol. Extending the example to feature requests 1 and 2, if the company hosts the file on a server from which their designers’ computers can access it, they could simply link to it instead of embed it so that changes to the master logo file occur in real time to all Affinity documents that link to it.

Feature Request 1: Consider allowing all applications in the Affinity Suit to link documents like Affinity Publisher.
Feature Request 2: If/when linking across all Affinity Applications is possible, consider allowing the user to select not only select a specific art board or the entire document but also any layer at any level in the layers hierarchy of a linked or embedded document.
Feature Request 3: Similar to linking, consider allowing for application-level symbols. Currently, symbols only exist at the document level. Such a feature achieves the same ends in feature requests 1 and 2 on the same computer.
—
For example, if a company creates a logo that is to be up to date in any subsequent work such as app and website UI mockups in Affinity Designer, print-like publications in Affinity Publisher, and photos in the editing stage in Affinity Photo, it would be great if feature request 3 is implemented to allow for an application-level symbol to hold that logo so that any changes to it synchronize across all other Affinity documents containing this application-level symbol. Extending the example to feature requests 1 and 2, if the company hosts the file on a server from which their designers’ computers can access it, they could simply link to it instead of embed it so that changes to the master logo file occur in real time to all Affinity documents that link to it.

Hi @tidbit, welcome to the forums!
 
I would actually like to extend the subdivision request to include an option to subdivide along a linear axis in addition to the mode you are suggesting which accounts for the shape of the path.
In other words, one option would subdivide based on the flattened path length, as your example shows, while another would divide evenly along the horizontal (or vertical) axis, wherever those points happen to fall along the length of the path, and another would subdivide evenly based on a straight line drawn between the two end points of the path.
I think all of those options could be useful at times.

Posted on reddit a while ago: https://www.reddit.com/r/AffinityDesigner/comments/du0ejg/evenly_subdividesplit_a_path/
Inkscape (and blender, while we're at it) seems to be the only vector program that has something IMO is so simple and commonly used (atleast by me, and blender users). The ability to subdivide an object/selections nodes, placing new ones perfectly spaced apart. It's one of a few things holding me back from using affinity.
Additionally, vice versa: Simplify/decimate. Remove all unnecessary nodes but keep the overall shape (some distortion is to be expected, but it usually does a really good job)
Attached, or on the reddit post, is an example gif using inkscape