R C-R

Nothing like Anime Studio's edge removal tool in AD. To eliminate a stroke between two nodes, you have to use the node tool to select the nodes one at a time & use the Break Curve action from the context toolbar to separate the curve into two parts, then delete the curve section you don't want.

Alternately, for some drawing tools you can hold down the alt/option key & drag in the workspace. You get the same magnifier that shows pixels as with the Color Picker eyedropper (which isn't a tool in the normal sense & doesn't appear on the tool panel). To see which tools support this, look at the text at the bottom of the window after you have selected one. The text indicating if the alt/option drag is available will appear there. Many of us have asked for a more conventional Color Picker tool like PS & several other apps have, but if or when that will be added is unknown.

I think only you can answer this. Like anything else, learning something new can take considerable time, but the skills & understanding that comes from that may help you in ways you can't anticipate, often with things that seem unrelated until much later. Regarding getting "good enough" for decent edits, it depends a lot on how good that needs to be for any particular purpose, but if you like to learn & can generate a reasonable amount of creative inspiration, you should be able to invest a lot less than 150 hours before you know if what you want to do justifies investing in more learning time or if it would be more time & cost effective to hire someone to create it for you. If you are primarily focused on logos, I suggest starting with Affinity Designer & "graduate" to Photo if & when you need its more comprehensive bitmap editing features. If you have never worked with a vector graphics app before, there will probably be a steep initial learning curve "bump" but once you get past that, it will get easier & most things you learn will apply to AP as well, making that app easier to learn more quickly.

Short version: no. Longer version: Affinity Photo is an OS X application, as is the OS X version of Apple Photos. The iPad runs iOS, which is similar to but not the same as OS X. The iOS version of Apple Photos has a limited number of features compared to the OS X one, & does not support extensions written for OS X.

Nothing? Am I the only one interested in this? :(

What about "Macros Persona" (plural)? I suspect the developers do not want to use "Action" because it would be too much like PS. Alternately, maybe just make the "tooltip" for it more descriptive instead of just displaying the name (which we probably already know)? Something like "Create & use macro commands"?

Almost! If you have an Affinity app icon in the Dock (like I do), yet another one is very similar to your first one & probably easier than the method I suggested: Control or right click on the icon to bring up the menu of recent documents, Options, etc. Then hold down the Control Key & select "Open," the last item on that menu. This is almost the same as my method but avoids having to get the timing right when pressing the Control key. I haven't looked to see if it is already there, but this might be a worthwhile addition to the Tutorials forum area. It doesn't have to be a video or too elaborate, just something that lists all the options.

"Start the app with Control held down." Unless I am missing something, this often suggested step to get to the clear menu on launch can be a little misleading. That is because (at least on my Macs) holding down the Control key before trying to launch the app anywhere besides in Launchpad will just pop up a contextual menu. The only thing that works for me is to wait until the app starts to launch & then as soon as possible after that hold down the Control key. Since I have no use for Launchpad & keep the Affinity apps in the Dock for quick access, what I do is click on the app in the Dock & just as it begins its first hop, press & hold the Control key. David4, If clearing the app doesn't help, as a last resort you might try starting up in safe mode & then restarting normally (no need to launch any app or anything else while in safe mode). This will delete system caches, which will be rebuild as needed when starting normally. That will slow down some things temporarily as a cache gets rebuilt, but once rebuilt won't have any lasting effects. This step will fix problems that are caused by corrupted caches.

Yes, several of them & they are installed automatically with AP. Enable them in System Preferences > Extensions if they don't appear in Apple's Photo app's edit panel.

For what it is worth, I get the same calculating forever results with the PDF X1-A export preset after resizing the image to 40 mm wide. However, if I rasterize the image before trying to do the export, I don't have any problems. I also noticed that before rasterizing the image, in the export dialog box, just like in imacken's last screen shot, next to the Raster DPI setting, it says "(Nothing will be rasterized)" whereas after rasterizing it says "(Some areas will be rasterized.)" That doesn't make any sense to me since this is a bitmap image, so either way it should be rasterized on export.

Look on the Context toolbar for the shape options that appear when you select the Curve tool. The last two are Convex & Cutout. One of them should do what you want.

From your example, try opening "Space Dock" or "The Visit" by clicking on one of them in the AP Welcome window. (The lack of the cloud icon near each of them indicates they have been downloaded.) Now, once the file has opened & you can see it in the workspace, open the File menu & look for the "Reveal in Finder" menu item. Choose that & a Finder window should open to the window where the file is stored.

Any time you reduce the size of an image by resampling it, the number of pixels in the image will be reduced, causing its quality to be degraded. This has nothing to do with Affinity or the resampling method used, although the latter can minimize the visible effects, as does the content of the image -- purely rectilinear elements will show fewer jagged edges & look less burry than ones with diagonal elements when resampled. If you are not resampling (the box is not checked) then you can only change the dpi, which will affect only printed output & related items like the ruler units. The Understanding DPI video tutorial explains this in more detail.

They are in a folder in /private/var/folders/. The exact location can be found with the Affinity File > Reveal in Finder menu item when the file is opened in the workspace. If you are worried about the file space they use, you can delete them from there, or just wait until you next restart the computer, which will clear the folder's contents automatically.

Regardless of the method used (Affinity media browser or File > Open > Media > Photos) it will still take a lot of time to scan a 200+GB Photos Library of 36K photos. What you see in either one is not a folder but the System Photo (or current iPhoto) library, which is really a complex structure of multiple files & folders (a package, in Apple terminology). For a Photos System library, once the initial access has finished (which can take several seconds even for a modest sized library stored on an internal drive) you should see all the same categories as you do in the Photos sidebar -- Moments, Collections,Years, Places, Albums, etc. Each of those items is subdivided into smaller groups just like it is in the Photos sidebar. Since that depends on how your photos are organized & categorized in Photos, there is no way to tell you which is the best or fastest one to find the photo you want. Regarding which of the top level libraries are essential, it depends. If you had the old iPhoto library installed on the system startup drive, when you first opened Photos & it "migrated" that to a Photos library, it would not have duplicated anything -- it just would have created links to the original iPhoto files in the new Photos one, as described here. However, when the old iPhoto library is not on the startup drive, things get complicated. The links created are hard links (not aliases or symbolic links), which can't span different file systems. So either the migrated library is created on the same drive as the old iPhoto one & there are no duplicates, or (more often) it is created on the startup drive & everything is duplicated. Likewise, if you move the library from a drive that is using hard links between the iPhoto & Photos libraries on to a different drive, the hard links won't work & Photos creates a Photos library that duplicates everything to the destination drive. Also note that the hard link creation thing only works during the initial migration -- anything added to either library after that is unique to that library.

I am having a lot of trouble understanding what your problem is. Color palettes can only be accessed from the Color Palettes tab of the Apple Color Picker (the third tab from the left) but that is expected -- it is why that tab is called the Color Palettes tab. The Color Sliders tab (second from the left) has nothing to do with picking colors from a palette, just from setting them with the sliders, so there is no reason to, nor way to, use it to pick colors from any palette. What the Color Palette does allow you to do is change the color profile (not space) of the document, & of course this will change the value of any colors based on that profile.

You have to get the timing right when you launch Affinity Designer with the control key held down. It can be tricky to do without activating an OS X popup menu instead. I have had the best success from the Dock by clicking on the icon & then waiting very briefly until the icon just begins to hop & then pressing the control key as soon as possible after that.

Is there a detailed list anywhere of what gets reset when the various options to clear user data are used? Some seem obvious, others not so much. Related, what if any are the differences between using the startup clear options & the similarly named ones in the Preferences > Miscellaneous panel? Also, which user preferences, if any, are stored in plist files that could be examined or copied to restore them if clearing them does not improve anything, & where are they stored? The reason I ask is the often suggested solution of clearing everything to fix some issue requires tediously resetting a lot of items.

Leigh, thank you for that little tidbit about the color profile Apple's Color Picker uses. It is one of the things I have wondered about from time to time, but did not know who to ask. These forums are a great educational resource for me, not just for Affinity stuff but also for miscellaneous things like this. :)

For separated mode, as an alternative to the current default behavior I would not object to a preference to instead open documents at 100% where possible, but I would be very unhappy if it was an unchangeable default behavior. That is because I use separated mode primarily to work on multiple documents and/or multiple views arranged all over the screen (& sometimes on a second monitor), along with various "docked" & "undocked" Studio & other panels. So unless they are all small documents (& for me they almost never are) it would be very annoying to have to reduce the size of every newly opened window so that everything would fit without obscuring the others, & more annoying still if they just opened in some area where there currently is no other document window at whatever size that area allows (which would constantly be decreasing in size as more of the screen space was used). The current behavior isn't perfect for this kind of workflow either, but at least it is consistent & because it cascades newly opened windows it (usually) makes it relatively easy to select whichever one I want to move to some other screen position without having to move others out of the way. If anything, I would prefer that in separated mode every newly opened document opened in a considerably smaller window than it does now. This is what I meant about not being able to please everyone. What I would like is essentially the opposite of what you want, & I'm sure there are others who would want something different from either of us.

The Export persona allows you to export files in various formats, some of which are suitable for inclusion in web pages, but it is not a webpage layout app. The Pixel persona has some photo editing features but it is not as full featured as the personas in Affinity's Photo application.

If you just want to know the RGB hex code for a pixel under the pointer, the Info panel can show you that. It defaults to showing the RGB decimal & CMYK values but if you click on the half circle icon of either of them, you can choose to change what it samples. One of the options is RGB Hex. You can also click & drag the sampler's crosshair icon into the workspace, which turns into a magnifier. If you drop it somewhere in the workspace, it stays there & "freezes" the sampler's values in the info window.

For me that isn't exactly what happens. Depending on the image size, the amount it is zoomed before hitting Window > Zoom, & the current window size, the window may resize to (according to the View menu checkmark) "Actual size" or to "Zoom to Fit." This happens even when the actual size of the image is small enough to easily fit on the screen, & often the two window sizes are considerably different. Also, when the image is considerably larger than would fit on the screen, when I first open it the window is large & the image is zoomed to fit, but the window does not use all of the available screen space -- there are still unfilled margins to the right & bottom of the window of variable size. Hitting Window > Zoom in this case resizes the window to eliminate the borders & fills all the available space, but it leaves empty margins inside the window on the left & right sides. Preview's preferences also allows users to define "100% scale" two different ways, one with an image pixel equal to a screen pixel & the other with the screen size equal to the printout size, & to define that separately for PDF's & for everything else. In other words, even actual size & 100% size are variable, depending on if they are references to screen or printed output sizes. Apple has changed how all this works several times with different releases of the app & OS. As a former long time frequent contributor to Apple's user forums, I am all too well aware that every change has pleased some users & outraged others. I believe the same thing will happen no matter what Affinity changes -- some users will love them & others will think they are the stupidest, most illogical things they could have done.

Unfortunately, I am still a long way from figuring out what works best for me for things like this. I have discovered that the selection brush does work on a pixel layer with the 'all layer' option enabled to make pixel selections in the intersections of overlapping open paths or closed shapes, sort of like what you posited in an earlier post, but (as you probably have guessed) this isn't very useful because anything filled in is on a pixel layer & thus is not resolution independent, making it kind of pointless to apply it to vectors. It is a very good way to create jaggies though. :lol:

Like JimmyJack & I suspect most users, I want to see all of the image when I first open a document. I also almost never work with documents small enough to fit on screen at 100%. I suspect this is true for many if not most users. After all, even most point & shoot cameras & smartphones take photos upwards of 3000 pixels on the long dimension, as are A4 or U.S. letter sized pages. Images destined for the web typically are much smaller, but it is not unusual to work with much larger 'native' documents & only export to a web-friendly size later on. I am using a 27" iMac with a 2560x1440 pixel display, & I know a lot of Affinity users are using Macs with smaller screens. I think this has a lot to do with why 100% is not the default zoom level -- in a very real sense, "Zoom to Fit" is the only practical "one size fits all" default zoom level. Of course, this doesn't explain why in separated mode document windows don't by default open to fill the available screen space. I said "available screen space" because depending on the layout of tool, toolbar, & Studio & other palette windows (which all have variable sizes & positions), that won't be the same for everyone. I think that is part of the explanation for this default behavior: consider that some users won't want the document window to extend behind any of those UI elements, while that is exactly what others do want. So this is yet another thing where "one size fits all" will not apply. Another part of the explanation is probably something Thorworx touched on: it is not unusual to have multiple document windows open, & a major reason for using separated view to begin with seems to be able to see more than one of them at once, something that can't be done in the unified workspace (non-separated) view. Also, this isn't confined to different documents -- don't forget Affinity can display multiple views of the same document, each in its own window. There isn't much point in that unless the windows can be displayed so that at least part of each of them is visible at the same time. There are other things to consider that complicate this even more, like that some users use multiple monitors and/or multiple OS X "spaces," & that the different supported OS X versions (10.7 through 10.11 currently) treat these things slightly differently. Whatever we would like to see as the default or preference-settable options would have to take all that into account. Personally, I have no idea how this could be done without making it a nightmare for users & programmers alike -- for example, imagine upgrading the OS only to learn that your preferences or whatever don't apply anymore. Please don't get me wrong. I definitely think there are improvements that can & should be made to the window/workspace/zoom/default UI stuff. My point here is just that there are no straightforward, obvious ways to do it that will make everybody happy.