walt.farrell

If you want to be using a 10px grid, you would use a Standard Grid, not the Pixel Grid, and set it to 10px. You would then use Snapping options of Snap to Grid. And probably many/most other Snapping options off. But I don't produce your kind of art, so I can't say much more than that; sorry.

Move Data Entry is a desktop function only. The new Pixel Grid is a 1x1 px grid. It will only show when you're zoomed-in enough that individual pixels could be visible, and is enabled separately in the Grid settings here:

It would be easiest to figure out if you can provide a sample .afpub document that demonstrates it.

I doubt anything like that would happen before V3, if then. It is such a different kind of brush, and it would need to be added such that Designer would support 3 kinds of brushes: pixel, vector (as it currently is), and "true vector". But only Serif staff would know for sure.

It's only available in the Edit menu, but that's basically the same thing, and arguably faster as it doesn't take a long-press + a tap, just two taps.

I think I recall something similar (and perhaps logged as a bug) if one has a huge Assets category selected in the Assets panel. There was an icon-related category (shared in the Resources forum?) that could demonstrate this, as I recall.

As a partial workaround, you can save a Print Profile from the Print dialog, and if I remember correctly that will encompass both the Affinity dialog settings and the Windows printer driver settings. Then you could use that Profile when printing later. If it's not remembered with the .afpub document when you Save after you Print, then at least with good naming conventions you could easily find it to use later manually.

Too bad it's Apple-only.

So pick one that lets you define the grid sizes, such as Standard (as I mentioned above when I said "except Automatic").

You have configured it, because you showed it in 2 columns, which is not the default. I cannot easily say if something else is different, but that obviously is. Whether that would be sufficient to prevent the addition of a new tool automatically (or whether it should be), I cannot say. Someone from Serif who would know might comment.

It would be more efficient, I think, for you to tell us a specific part of the process that you're having trouble duplicating in Photo (and, as Garry mentioned, the time-code in the video).

I wasn't quite sure where to report this. I'm on my iPad (now at 17.1.2), using the standard browser (Safari?), and looking at the online Help for Designer 2 (desktop) 2.3. There are new options when you click Search in the Help's sidebar, and there's a row of options that looks very strange. If it's not a bug, and is intended, please explain what they do (and maybe adjust their display on-screen ) --

Just to be sure you know: https://affinity.help/designer2/en-US.lproj/pages/ObjectControl/objectGrids.html Tutorial: It's not completely what you're asking for, but much simpler than the old way.

That sounds like a bug which should be reported if it hasn't been already.

Have you tried simply dragging the Designer window larger rather than using full-screen mode? That might provide a workaround.

The only solution for now is to uninstall fonts, as far as I know.

In Settings, Assistant Settings, Develop Assistant, are you developing to RGB/16 or to RGB/32. If you're using RGB/32 try setting it to RGB/16. If that doesn't help enough, or if you're already on RGB/16, you can try RGB/8 but you'll probably want to use a batch job for that. Having said that, though, I would also recommend using a Batch Job to Develop them all to TIFF, and then generating the panorama from the TIFF files rather than from the RAW files.

You can switch back to 2.2, but it won't be able to Open any file you Saved with 2.3. You can download prior V2 releases of Publisher for macOS from https://affinity.store/update/macos/publisher/2 Have you verified that the field names in the JSON file match the field names in the Fields panel of your .afpub file? Do you have a .afpub file and a .json file that you can share which demonstrate the problem?

Yes, that would be nice. As a workaround in the meantime, rather than saving a Preset in the Develop Persona you can record a macro, and save it in your Library, and use it on other images to apply that set of Develop adjustments to other RAW images. In some ways this may be even better than Develop Presets, as the macro can be used in Batch Processing.

Also, I'm not sure why you've posted this as a bug. The FAQ lists the currently supported cameras and lenses. If your lens is not in that list, a request to add it is appropriate, but it should be a feature request in the Feedback forum. It wouldn't be a bug unless it is listed in that list, but doesn't work properly.

I recommend you remove your email address from your post. It will attract spam. It is an important piece of security-relevant data, and exposing it weakens the security of your account (unless you have 2FA enabled for logging in here).

It is not a bug, but intentional behavior. An Image Layer is a container, and you cannot access its individual pixels using a pixel selection and Copy. However, you should be able to do so via Edit > Copy Merged in Photo 2.

View > Configure Tools should allow you to add it.

Photo should be able to edit it, too.

I agree; the applications should do a better job of reacting to the current set of monitors you have available.