Paul Huckstepp

Ideally, yes using sync folders would be the way to go. Unfortunately, the pCloud in question is used by more than just myself (shared pCloud folder) and there is a very large amount of folders and files involved - hence using pCloud. For the time being I will copy the file to my local PC and then copy it back to pCloud afterwards. I also have a support request with pCloud who are looking in to the issue as well. As it seems that the issue is caused by pCloud syncing the file when it's open and locked and that is causing a disconnect between the application and file. Other cloud providers I've tried don't have this issue (iceDrive, oneDrive).

I too am having this issue when working with a file within a pCloud folder that someone else has shared with me. I'm using the Windows versions of the Affinity suite. As far as I can tell it doesn't happen when I use a file that is in a folder on my pCloud; just from within a folder shared with me.

UPDATE: When I changed my monitor to 100% magnification (4K monitor) and opened Publisher the Hyperlink dialog window finally appeared at the very bottom right of my secondary monitor. So, it would appear that when I adjusted to 125% UI the window was moved outside of my monitors display area making it impossible to grab and relocate. So. All fixed.

Hi. I have 2 monitors (4k and 1080p). The dialog isn't showing anywhere. The main window locks up to suggest that the dialog has to be shown but clicking the main window doesn't display it anywhere. The Insert Anchor on the other hand popups up in the middle of my main 4k monitor.

In the latest Affinity Publisher 1.9.1.979 when I click either the New Hyperlink button on the Hyperlinks window, or use the right click > interactive > Insert Hyperlink menu item the main window locks up and no hyperlink editor dialog is displayed. I can press the ESC key to get the main window to work again. The problem doesn't seem to affect any other dialog windows such as Insert Anchor - that displays just fine. I did think it might be a compatibility issue with Microsoft Power Tools FancyZones, or Stardock Groupy, but I can quit both of those and the problem persists.