lepr

To give Artboard properties to a Curve/Curves/Shape object, use Layer > Convert Object to Artboard.

To give Artboard properties to a Curve/Curves/Shape object, use Layer > Convert Object to Artboard.

OOf, long day and too many new software releases....lets try this again!
Hi!  I'm AD!  aka The Explorographer.  Photographer/creative from the Finger Lakes region (FLX) of NY.  (Near Rochester).  New to the forums, but I have been an Affinity Photo user for quite a while.  Just found this place through the beta program so I thought I would say, "Hi!".   Always looking for new photog/crative friends in the area so if you are around me, please say hi!  Let's share ideas, techniques, locations, whatever!   Glad to be here!

Here are a few pieces of my work.

That's cool. I wasn't trying to be the forum police. Was just letting you know. I've given your request a 'like'
 
 

Hi!
Sometimes I miss an option to stroke vector curves in Affinity Photo with its pixel brushes. It is a very helpful feature to e. G. give text a brush outline or for clean and smooth drawing and retouching with every tool. Of course it is possible to do a part of this in Designer, with its brushes. But that is a bit limited, I think. I used to work with this feature in GIMP and Photoshop for a long time and I would like to have it in Photo too.

Too late, I recently requested it again.

The functionality has been requested many times in the past 7 or 8 years.

You don't seem to know much about it, thus you better inform yourself about it, so what it does as a package manager and how it does all the stuff it offers etc.

Some of this year's reduced tree motives which I use on xmas cards ...




 
If you need some last minute xmas tree resources take a look under the forum resources at ...
Xmas Trees Assets Xmas Trees Xmas Silhouettes ... generally take then a look at the xmas stuff under ...
Retrospective of resources contributions
 
Have a contemplative and peaceful Christmas time!

In this sense ...

... not made with ADe v2.3, but ADe v1.10.7 instead (all vectors btw).

BerlinFX.

Affinity automatically considers colours to not match when their definitions are in differing colour models, therefore an RGB fill search will never find something that has an HSL fill, and vice versa.

Affinity automatically considers colours to not match when their definitions are in differing colour models, therefore an RGB fill search will never find something that has an HSL fill, and vice versa.

In Affinity Designer, the absence of a continuous corner radius tool limits the efficiency of designing UI elements. I strongly recommend the addition of this feature to facilitate the creation and iteration of UI designs. Consistent corner rounding plays a vital role in achieving a polished and cohesive look in UI design. Moreover, designing icons or UI elements for iOS, which extensively uses continuous corner radius throughout its entire operating system, requires the ability to apply continuous corner radius. By incorporating a continuous corner radius tool in Affinity Designer, designers would gain the capability to precisely adjust multiple corners simultaneously, with varying radii, resulting in smooth and visually appealing user interfaces. This enhancement would empower UI designers and elevate Affinity Designer's capabilities in the field of UI design.
Figma has a similar feature.

Users have been coping with the name of Transform Panel without your suggested documentation, so they'll probably cope with the name of Point Transform Tool without that documentation.

At least for me that only works in the Pixel persona of AD. I often forget that I need to switch to that persona to do that so I end up editing the document in AP needlessly. ☹️

Just to confirm, the above is logged with our development team and I have 'bumped' this with them now to bring it to their attention once again

My secret wish is that more Natural Intelligence is being seated in front of computer displays.  

"…but not if you press shift"
So?? It doesn't scale if you press Ctrl {Windows} either. But without pressing a modifier key it both scales and rotates in one move. So how would "scale" be a more appropriate name than "transform"?
Look; I'm all for intuitive and consistent terminology. And I've been at this for a while, too. I cut my vector-drawing teeth in Altsys Fontographer—the progenitor of FreeHand, before Illustrator even existed—on a Mac Plus. But egads, man, there's no real issue in this instance. Dear departed Aunt Mollie would call this "straining at a gnat to swallow an elephant".
For a real interface terminology issue, look no further than the current abuse of the "Pages" (or Artboards) and "Layers" terms. What is intuitive about starting a new document which displays a working area that certainly looks like a  page, drawing an ellipse on that 'non-page', and having the ellipse immediately listed in a Panel named "Layers" in which there are no Layers (or Pages)? Since when is a single ellipse a 'Layer'? This is supposed to be intuitive terminology convention? But we should take issue with "Point Transform Tool"?
Illustrator is historically one of the worst about needlessly renaming its so often late-to-the-game constructs and features that existed long before in competing programs. Calling pages 'artboards' and nodes 'anchor points'. Its utterly needless and wordy 'Convert Anchor Point Tool'. Starting the whole now pandemic 'necessity' for two primary selection tools—the second of which is awkwardly named the 'Direct Selection Tool'—when FreeHand's elegant single selection tool performed all the functionality of both, more efficiently, intuitively, and capably. Adobe should hardly be considered the authoritative preferred 'dictionary' for best feature naming.
So yes, I quite agree that words mean things. But functionality still trumps. The functionality of the Point Transform Tool addresses crucial omissions that stem from having only bounding box handles for common transformations: being able to rotate paths by their nodes, so as to intuitively snap them to paths and nodes already drawn. Before the Point Transform Tool, that was a serious failing relative to Illustrator. It's actually a bit of a new wrinkle and more elegant and accurate than the corresponding functionality in Illustrator.
Pen Tool: Draw three arbitrarily-shaped open paths; one near the upper left corner of the page; one near the lower right; and one in the middle. Your goal is to scale and orient the middle path—without distorting its shape—to perfectly fit between two arbitrary nodes; one on the upper left path and one on the lower right path. Point Transform Tool: Select the middle path. Mousedown on one endNode of the middle path. Drag and snap it to the target node on the upper left path. Drag the Transform Center and snap it to that same node. Mousedown on the other endNode of the middle path. Drag and snap it to the target node on the lower right path. Done. Tell me how you would do that as quickly and intuitively in Illustrator with one tool. "…do we need a [term like] 'Point Transform Tool' that…makes little semantic sense to most people?"
Yes! We need different terms for interface elements that are significantly different treatments of similar functionality in other programs, so that we know they're not just another re-packaged 'me, too' identical copycat treatment of same-old market-dominating (and progress stifling) programs like Illustrator.
I cringe every time I see users in forums like this demand "We must have a [insert Illustrator's term] tool in Affinity!", as if Illustrator's cluttered, confused, scattered, and often mediocre treatment is the ultimate de facto thing to emulate. Affinity is opportunity to finally advance 2D bezier drawing beyond the mediocrity of Illustrator. But it won't get there by just thoughtlessly demanding identical treatment from such long-in-the-tooth programs without putting at least a little thought toward how it might be done better.
 

Also translates (aka moves) objects.
Translate, scale and rotate are transforms. The name of the tool seems appropriate.

So… obviously not: https://tinyapps.org/blog/201902200700_contact_sheets.html
But as noted on the aforelinked page, the contact sheet solution is still built in in MacOS as of Ventura, and it works. Just tested.
in Finder select Go menu → Go To Folder paste the following path and press Return:
/System/Library/Image Capture/Automatic Tasks create an alias of the MakePDF app somewhere in your home directory for future easy access launch MakePDF File → Open → select which ever images you want
or drop a folder with images onto the MakePDF icon in Dock or on your alias in Finder in the Layout menu, select your layout or create a new one save voilà Same for the Build Web Page app in the same location. It has a few adjustable settings like image sizes and background color. The generated web page directory will appear in your ~/Pictures folder and automatically open in your default browser.
~~~
Conclusion:
Even after 35 years on Mac and 23 years with OS X, I can still learn new tricks I had no clue about!  

Designer_BKiRSL6KQB.mp4

I think vectorising the letters and using a single colour would modernise your brand logo, like so.

Celeste Press Logo.svg

An alternative version using Inner Shadow instead of Inner Glow because the latter lacks angle and offset controls.
drop.afdesign

 

Yes, there is inconsistency and it is a bug. You have received flawed excuses/explanations and workarounds that should not be necessary.
When a Content object (an Image, for example) of a Master Page's Picture Frame is accessible on a regular page without a requirement of invoking Edit Linked/Detached, a child (Adjustment or Mask, for example) of that Content object should be equally accessible, but instead the child wrongly has the same restricted accessibility as a non-Content child of the Master Page's Picture Frame.
As you know, we can add a child to the Content object of a Master Page's Picture Frame when we work on a regular page without invoking Edit Linked/Detached, and immediately edit that child before it becomes deselected, which is sensible. It is nonsensical for that child of the Content object to later be uneditable without invoking Edit Linked/Detached.
A bug.