walt.farrell

What kind of GPU do you have, @Linktros? In your application Settings, what do you have in the Performance section? If you have Hardware Acceleration (OpenCL) enabled there, please try disabling it, restarting Photo, and seeing if that resolves your problem. By the way, if I copy that layer and immediately paste it back into the document everything works properly on my Windows system.

Thanks. No, there's no possibility of a keyboard shortcut for operations using a panel's Settings dialog. I would expect Publisher to remember your Pages panel thumbnail size for each document where you've set it, though. If it's not doing that, I would start by seeing if that failure to remember a document setting is a bug.

You might also try rebuilding the Windows icon cache, e.g. as described here: https://answers.microsoft.com/en-us/windows/forum/all/how-to-rebuild-icon-cache-clear-thumbnail-cache-in/1e45604c-c8e2-4d6b-9e32-77f07e07bc17

You can't update object Styles. Your easiest approach is probably: Assign the existing Style to an object. Change the object's styling. Create a new Style from the object. Delete the existing Style you wanted to update. (You could interchange steps 3 and 4, if that's simpler.)

Sorry, but I'm having a hard time figuring out what you want to do. Can you provide a specific command you want to perform on a specific object, to help me understand? Thanks.

If the "images" are actually Linked PSD or Affinity files (.afphoto, .afdesign, .afpub) rather than actual images (JPG, TIFF, PNG) then you might be experiencing a known problem logged as AF-6599. The workarounds that have been suggested so far include: Converting the missing files to actual images (TIFF, JPG, PNG). Converting the .afpub document to non-Facing pages (which may involve some rework of content placement on the pages. Reverting to an earlier release. 2.5.7 should work, though it won't be able to Open any Affinity files saved by 2.6.0 or later. But you could also try reverting to 2.6.0 first, which might also work and will be able to Open all your Affinity files.

Rather than Exporting, your best approach would probably be to use File > Save to create a .afphoto file, and upload that. Your topic wouldn't have been deleted because you failed to respond, but for some other reason. Unfortunately, only the moderator who deleted or hid it could say what that was.

You're welcome. And no, there isn't a solution near-term, unless Serif suddenly releases their Scripting feature.

If you're getting a message that some function cannot be recorded, then you have found one of the many limitations of the macro recorder. For example, you can't record File > Export, either, and you should find it gives a very similar message.

If you did not explicitly use File > Save (or the shortcut for it), then it was not being Saved. By default, every 5 minutes a backup should have been saved (or updated) so that, if the system or application crashed, your work would not be lost (except for part of the last 5 minutes). But that is not really "saving", and is often unreliable for some users. If it was working for you, then if the application crashed: If you were working on a file that was unnamed and had never been Saved, when you restarted the application you should have gotten a prompt to recover the file. If you answered Yes, you should have gotten the most recent backup that had been automatically created. But if you were working on a named file (one previously Saved), then you would only be prompted for recovery when you try to Open that file again. (This is further complicated by application and OS settings to automatically reopen files, so it can be difficult to explain how it works in all situations.)

Yes, you were asked to create a new topic, but you should have created it in the same forum (Desktop Questions) that you were in before. The Resources forum (where you created this topic) is (as it says at the top, for users to share custom brushes, textures, etc. that they have created. It's not for asking questions or seeking help. A Moderator can/will move it for you, so you don't need to repost again. In the meantime: You indicated you're not using any kind of cloud synchronization, but I see you're on a Mac, and using your Desktop folder, and that would normally be managed by iCloud, I think. Are you sure it's not enabled for iCloud synchronization? You also indicated that you're saving to internal, external, network, and USB drives. Of those, it's unfortunately really only safe to save to internal drives, and then you can use Finder to copy the file to some other location. Can you share the .afpub file with us publicly? If not, you may need to wait for a Staff member to provide a private upload link. However, there are a couple of approaches you can try to recover it yourself: a. Create a new document. Try to use Document > Add pages from file to copy the information from the corrupted document. It may be necessary to try to copy individual pages, or ranges of pages, rather than the complete document. or b. Create a new document. Use File > Place to try to add the document one page at a time.

It sounds like you were painting on it while you still had the pixel selection active, and in that case the action of painting is restricted to those selected pixels. As that could be a very small area, are you sure you would have noticed the effect of either painting? Are you sure you even painted in the area of the mask corresponding to those pixels?

You're welcome.

And there is also still the 25% upgrade discount for users migrating to V2 from Affinity V1, so not as good as the initial 40% discount but still significant.

PNG won't work, as PNG doesn't support CMYK. But that won't explain your problem with TIFF and JPG. TIFF, by default in Affinity applications, will be Compressed. You may need to set compression off in the Export options.

Then you can either: Don't work in 32-bit within Photo. This may involve changing your Photo Settings (Affinity Photo 2 > Settings from the macOS menu), and then in the Assistant section of the Settings tell it to use RGB-16 for the output of the Develop process rather than RGB-32. Working in 32-bit mode has many complexities and isn't intended for normal users doing normal work, but for specialists. or When you Export to PNG, make sure you choose the basic PNG Export Preset, but then in its options, for Pixel Format, specifically choose RGB-8 or RGB-16 from the options. And, perhaps, create your own Export Preset that you can use so you don't have to remember to change the Pixel Format option every time.

First, your choices are MSIX or MSI/EXE. It's important to get that terminology and distinction correct. MSIX has advantages. And MSI/EXE also has advantages. Only you know your needs and desires and (importantly) what other applications you have installed that may affect how you use Affinity applications. Examples: Some users want to launch the applications using icons on their desktop. That is harder with MSIX, so such a user might want MSI/EXE instead. Some users don't like the standard Windows Start menu, and replace it with 3rd-party applications. Some of those 3rd-party applications do not support MSIX, and so those users would want MSI/EXE instead, or they would need to change the application they're using to replace the Start menu. Some users have other applications they work with, and may want to transfer work from those applications into the Affinity applications, a kind of "edit in" or "open in" from the other applications that will launch Affinity applications. Some of those applications support using MSIX, but many require MSI/EXE as their developers haven't bothered to update them to support more modern Windows technology. Those users may want MSI/EXE instead. On the other hand, if you install MSIX then when an update is needed the application will prompt you and if you agree it will update itself and relaunch automatically. But with MSI/EXE you must do the download, and you must quit the currently-running application, and run the downloaded installer. And, critically important, you must remember that you need to download the MSI/EXE installer and choose it from the download menu. And you need to remember what kind of CPU chip you have installed so you can choose the proper version (X64, ARM64) of the MSI/EXE installer. Yes, it's fine to have both. And it's fine to remove V1, once you've installed and run V2 to migrate its settings and content (brushes, assets, etc.). But I would not remove it until you've cleaned-up your current V2 situation. You need to first decide which kind of installer you should be using. Then, I suggest you figure out (for each Affinity V2 application) which one is the MSIX and which one is the MSI/EXE, and uninstall the one that you don't want. Then run the remaining one and properly update it. To figure out whether an application was installed via MSIX or via MSI/EXE, you can do one of these: Use the Task Manager while the application is running. If you right-click on the application in the Task Manager one option will be "Open File Location". If the path to the file, as shown in File Explorer, includes the WindowsApps folder, it is an MSIX application. If it's an MSI/EXE it would have Program Files in the path instead, or wherever else you might have chosen to install it. Use Windows Settings. In its Apps section, if you right-click on an application that is an MSIX application, one option should be to Move the application to a different location. If you don't see that option, it is not MSIX, but MSI/EXE. Also, I think that MSIX applications will show as significantly smaller than their MSI/EXE counterparts, so if you have two versions of Affinity Photo 2, for example, and one is much smaller, that's the MSIX one.

First, if you're offered the option to Download, you're running an application installed using an MSI/EXE installer, so you want to make sure you download the MSI/EXE installer for 2.6.3, not the MSIX installer. Next, as Alfred mentioned, you'll need to quit the application, and run that installer in order to perform the update.

You're welcome. If the purpose is to support, e.g., multiple languages, it shouldn't matter that the Text Frames have been disconnected using Edit Detached. You can still have them in Layers (with a capital L) on the Master Page, and hide those Layers. You don't need to hide the individual Frames that way. But for more discussion it may be better to have a separate topic with a more concrete example of what you're trying to accomplish.

As I don't use any applications that support them, I would not be a good person to write that description. I generally trust what other users write about the functions/usage of Global Layers.

I said nothing about alternative approaches, such as global layers. Presumably they can be used in those applications that support them, and I did not say they were wrong. I commented that if setting up the layers on all the document pages took a thousand clicks, the user was not using Masters properly. Master Pages also allow automatic creation of the needed language-layers on all the document pages in one operation. Hiding language layers using Master Pages does not require States. You can simply navigate to the relevant Master Page, and in the Layers panel click the icon to hide the layer you don't want, and click the icon to show the layer you want. Two clicks at most, and all the layers are shown or hidden on all the pages with that Master Page applied.

Then you're not properly using Master Pages.

Perhaps it should be simpler, but trying to resurrect an archived discussion from 10 years ago won't result in any changes. If you want to see a change to the program, post in the Feedback & Suggestions forum.

That may depend on why you're removing the metadata. As you've learned, ICC Profile and Metadata are different, so it's up to you to figure out what you want to do, and why, and then do it.a Note, though, that if you remove the ICC Profile for a JPG file, and it's RGB, many applications including web browsers will assume it's an sRGB file. If you remove the ICC Profile and it's not an sRGB file, then those applications will display it incorrectly.

Too bad, but it seemed worth a try