R C-R

Affinity Photo has a Gradient tool. When you select it, the Context toolbar has several options, including context (fill or stroke) & Type. One of the Type options is "Bitmap." Select that & you can specify a previously saved image file (jpg, tif, etc.). Use it on a shape, such as a rectangle that covers the canvas, & you get Extend options & control handles that allow you to fill the rectangle with a repeating pattern. Use the Mirror or Wrap extend option for this.

So can anyone explain why I can scroll with the wheel & drag, even when "Use mouse wheel to zoom" is disabled? I can't do both at the same time, but as long as the mouse button is down, scrolling with the wheel works.

I think he means adjusting the layer opacity of the image and/or using the Overlay option to combine it with the other layer(s).

I am using a Kensington "Expert Mouse" trackball, which has a scroll ring that functions as a scroll wheel. Preferences > Tools has "Use mouse wheel to zoom" enabled, if that makes a difference. I can move a selected object anywhere in the workspace & simultaneously zoom with the ring. Independently of that if I move the object out the visible area of the canvas, the view scrolls left/right/up/down as required.

As for creating the texture from scratch, one way might be to take a few closeup photos of a piece of a plain white cotton cloth & create a bitmap from that.

What OS (Mac or Windows) & version (Win 10, Mac Sierra, etc.) are you using? I am using an iMac running macOS 10.12.6 Sierra & am not having this issue.

For what very little it is worth, this happens because in Affinity a straight line is considered to be a one dimensional object that has no area (the stroke width is ignored). So when it is part of a divide operation it is removed. For some unknown reason, the divide op also closes open paths, even if applied to a single open path. Even if the line is a two node open path, if you bend it slightly, that gives it an area, & the divide operation will work, but it won't help much because you end up with 3 closed paths, like in this divide op.afdesign example: It isn't obvious from the screenshot, but the black curve includes all the nodes of the blue curve & attempting to subtract the blue one from the black one probably will generate a bunch of extraneous nodes. That can be cleaned up, but you still end up with two nodes on the black path at the two intersection points, & deleting one of them will deform the shape at least slightly. Even if you don't delete one of them, the tiny segment connecting them is straight, so the curve is still deformed slightly. It ends up being an exercise in futility.

Snapping works fine regardless of the document units. But pixel alignment aligns to integer pixel values of the document so, since a point usually includes many pixels, if you are using points as the document units, you are likely to see the X & y positions of moved objects align to some fractional point value. Two different units but the alignment is the same.

@Mercsport 1. To update Affinity Photo you use the Mac App Store app ("App Store..." on the Apple menu), not iTunes. This is the same app you used when you bought AP originally. Sign into the store with the same Apple ID you used when you purchased it & click on the "Updates" tab. 2. The free offer will appear on the Welcome screen only after you update AP. 3. The updated version runs fine on El Capitan.

Your screenshot of the Transform panel shows values in points ("pt"), not pixels ("px"). What happens if you temporarily change the document units to pixels & try moving or resizing the rectangle?

I installed the JimmySans & JimmyScript fonts on my iMac running Sierra via Font Book. Because I selected all 10 fonts, I initially got duplicate warnings but after allowing Font Book to automatically resolve the dups, validation found no errors:

Again, on my Mac they are the same display size with either one.

I tried dragging the jpg from this page directly onto my desktop & also doing that from the 'full size' version that opens in another browser window, I get two differently sized files, one 1280 × 853 & the other 1000 × 667 px. However, for both of them there is no difference here between 100% & Pixel sizes. Can you maybe attach a zipped example of a file that gives you different results to avoid any effect this site or different web browsers might have on the file?

I am not so sure it is always going to seem simpler from a user standpoint. For example, once the sequence is complete, editing it to change the angles where two adjacent pie wedges meet would be much simpler if the start & end angles supported snapping. But I do understand that logically this would be difficult & probably not worth the effort.

Maybe this is some kind of Mac vs. Windows difference?

Do you have any Studio panels set to display on the left? You can do that by dragging Studio panels from the right Studio (or wherever they are if they are floating & unattached from the right Studio) until they are near the left edge of the workspace. When they are in position, they will highlight, similar to how that works if you drag panels around in the Studio to reorder them. Since you said "left menu" in your post, I was not sure if you meant Studio panels or the Tools panel. If you meant the Tools panel, the answer given by @toltec should set things right.

It isn't a contest so there is nothing to be sorry about. Your reply with the animation was more informative & easier to understand than mine anyway. Hmmm. They did for me -- that is how I made the file so quickly. Maybe it depends on the snapping options enabled? This is what I was using:

No angular grid that I know of but why not use pie shapes for this instead of circles, like in this Pies.afdesign example? EDIT: @Aammppaa beat me to it!

I see no difference in the screen display for either one. Do you?

Adding slightly to what @Lee D said, this article discusses how different cameras typically store RAW files using both compression & lower bit depths to save file space. Decompressing & 16 bit conversion during the development process would result in a lot larger file than the size of the RAW file suggests.

This has nothing to do with the version, only with the pixel alignment of the line on the canvas & its cap type: Try setting the cap to "Butt Cap," make sure "Force Pixel Alignment" is enabled, & if "Move By Whole Pixels" is also enabled that the x & y coordinates shown in the Transform panel are whole pixel values with no decimal fractions before moving the line. Otherwise, the line will not be pixel-aligned, resulting in the anti-aliasing effect you see.

If you mean Apple Color Emojis, on my iMac they do not work at all. I can add one of them to a frame or art text object from the Mac Emojis & Symbol viewer & they appear on the Layers menu & in the History panel, but not on the canvas or artboard.

According to the Zooming help topic, "document pixels map directly to screen pixels" at 100% and Aside from that not particularly helpful help, I can't find anything in the help about display sizes, nor have I ever been able to create an Affinity document in which 100% & Pixel size differ. EDIT: It occurs to me that for some raster file formats pixels are not necessarily square (the pixel aspect ratio is not 1:1), so perhaps for an imported file with a different PAR 100% & Pixel Size would be different?

The Affinity apps do not include any fonts. They can use whatever fonts are installed on your system, so if some are missing when you open an Affinity file on your laptop, it means you have not installed them on it.

1. You should have received an order confirmation email with your order number, a summary list of the items ordered, & the text "This is a free complimentary order" in it, but there are no product codes for the bonus content, & none needed. Check your email for an item from "Affinity Store" (no-reply@affinity.store). 2. There is no need to use a third party utility like the Unarchiver to unzip the files. The Archive Utility app built into the Mac OS will unzip zip files without asking for any user input. If you have set the Unarchiver app as the default to open .zip files, you can unzip the dirk-wustenhagen-fine-art-texture-collection.zip file by right clicking on it & choosing "Archive Utility app" from the "Open with ..." item in the menu that pops up.