R C-R

It might help understand better what he was doing if you posted a link to the video(?) where you saw this, or if not a video on the web than told us more info about where you saw this.

If you could upload a sample of just a master page & maybe one document page so we could see how you are setting pages numbers, it would probably make it obvious what you are doing wrong.

If both the top parent layer its two child adjustment layers are all highlighted like in your screenshot, try clicking once on the thumbnail of the adjustment layer you want to access, then when it is the only layer highlighted, double-click on its thumbnail. In all cases make sure you are clicking on the thumbnail icon on the left & not the name of the layer to its right.

Likewise 3 to 30%, 4 to 40% & so on. Also, typing 1 then immediately typing 2 sets opacity to 12%, typing 3 then 7 to 37% & so on. Typing zero twice in a row sets opacity to 0% & typing it just once sets opacity to 100%. This means it is possible to set a selected layer's opacity to any decimal percent quickly using just the number keys, but it also means there is no way to change these 'wired in' keyboard shortcuts because of the unique sequence of 2 keys shortcuts cannot use the same logic as the normal ones.

I would call it a tie. Your macros are (almost?) one step solutions but they only work in AP. @Pšenda method takes more steps but works in all the Affinity apps.

I hope @Furry would have mentioned it long before now if there were any keyboard utilities running on the system, but maybe not. Ditto for a non-standard keyboard, but who knows? But regardless, to me the only thing that makes even a little sense to me is something that could affect both AD & APub & somehow just a few of the default keyboard shortcuts.

Have you ever used a second monitor with your Mac? If so, the Resource Manager window may be opening on that, even if it is not connected.

But it should at least exist if there are no permissions issues preventing it from being created when @Furry alters any of the keyboard shortcuts, right? As I understand it, that file should be written to automatically whenever any change is made to the shortcuts in the preference. @Furry just recently said that there was a change made that was retained, just not the one for Duplicate, so it makes no sense to me that the file is completely missing from the Application Support folder. There is also the continuing mystery of why both AD & APub both seem to have the wrong shortcut for Duplicate & neither one (?) can be changed & retain the change on the next startup, & why the Serif Defaults button does not reset everything to the defaults, including for Duplicate.

I can't think of any way a leftover *.affshortcuts file could have any effect on loading a different one (since that should replace any leftover one) so it seems like the only thing that makes much sense at this point is some sort of permissions issue that is somehow preventing the app from saving the changes made to whatever the current keyboard shortcuts are set to when the app is quit. That seems very unlikely, but so does what @Furry just said about the only instance of an AffinityShortcut.affshortcuts file on the HD is in the download folder. Surely there should be a version of that file named "shortcuts.affshortcuts" in the Application Support folder, which I think for the Affinity app store install should be at path ~/Library/Application Support/Affinity Designer/shortcuts.affshortcuts if the changes he made in the preferences file actually are being saved. So at this point, all I can think of to check is the permissions privileges for every folder in the file path to that Application Support folder using Finder's "Get Info" function. All should show that Furry has read & write privileges. If not, that probably would explain it ... I think!

This is bizarre. I downloaded both the AffinityShortcut1.affshortcuts & AffinityShortcut2.affshortcuts files, & one at a time loaded each of them into AD on my Mac. They both did show the Option-Shift-CMD-S shortcut for delete, both in both I could successfully change that to CMD-J, quit the app, & have CMD-J remain for that shortcut on the next launch of the app. So it would seem that there is nothing inherently wrong in either of those two files that should prevent changing & retaining that shortcut to the app default, but what is preventing that from working for @Furry remains a mystery to me.

If you click on the Document menu do you not see Resource Manager... as the last item in that menu, or do you mean something else, like that the Resource Manager window does not open?

If you print only any one artboard, only items it contains will print, so if for example you want to print only your smaller artboard you have to make sure it contains the items you want in the print. That's just the way container objects like artboards work.

If you are asking if your template preserves the show bleed setting, why not just try it for yourself?

The problem with that is not everything that has effects applied to it typically is something you want to have the same fill color as every other item that has effects applied to it that you might want to remove in a single step.

Just as a matter of curiosity, how many other British software companies have put something on their home pages about it?

To me, it looks like there is a single "(Curves") object consisting of 4 individual curves (because there are 4 red nodes visible), but I do not know how the OP created that.

I think it is because "fx" at the bottom of the Layers panel is not a glyph or a pair of letters but instead a button icon, like those for mask layer, adjustment layer, etc. Like someone said, icons sometimes used to be something that could appear in Mac app menu items but maybe became impossible or at least not considered best practice once OS X was released.

Be that as it may, there have been multiple reports of problems caused by saving Affinity format files directly to a OneDrive location. It is possible this has something to do with the speed or reliability of the internet connection to OneDrive servers, but regardless, if the error goes away if the file is saved to a different location then in this instance it does point to a reliability issue of some kind between Affinity & OneDrive.

It may be different for Windows but in the Mac version's General preferences there is a checkbox for "Save thumbnails with documents." If that is not checked when the file is save, Finder just shows the generic Affinity document icon like in your screenshot, so you might check for something similar in the General preferences in the Windows version. Also, for the Mac Finder there is a per-window View > Show View Options item to "Show icon preview." Only if this is enabled will the Finder window show the thumbnail or preview; otherwise just the generic Affinity document icon is shown. So also check for something similar for Explorer.

It works fine for me, but I do not understand how you made its single(?) "Apply Object Style" step. Can you explain more about that? Specifically, how did you record an object style in a macro?

This is probably the solution because OneDrive & Affinity have a history of not working well together. If you need to add the file to a OneDrive location for some reason, you can first save the exported file to a local location & then copy it to OneDrive, & optionally then delete the local copy. A PITA but I don't think there is any other reliable alternative.

First, the idea is to add the object as part of the macro so that does not have to be done as a separate step. Second, no, I cannot get the macro recorder to accept the Edit > Copy menu item (or by using a keyboard shortcut or whatever) step. Have you tried recording that step in a macro yourself? If so, does it work for you?

If you can attach an example Affinity format file to a new reply showing what the layers look like before moving or subtracting anything, someone may be able to suggest something that will do what you want.

Possibly because there have not been enough requests to add that in the feature request forum. That seems like an OK but not great workaround because for it to work, the document must have at least one object that has no effects applied to it to copy. I was hoping I could create a macro that would add an object that has no effects, copy that, do the paste effects step, & then delete added object but I could not figure out how to include the copy step in the macro. Maybe someone else can?

Are you asking about the white lines that look like a reflection of a (fluorescent/) light on a pane of glass or something else?