Search the Community

Yes, on my desktop PC (Windows 10), I have two monitors, the bigger for the image and Affinity Photo on the smaller. For the greater part of the time, all is fine and works well. However, although the main program and the most used panels, such as layers, history, colour, etc are there, quite often when I use something like a filter or the warp mesh tool it opens on the bigger monitor and behind the image. To fix this, I minimise the image and drag the panel over to the smaller monitor. It is a pain when I have to do this several times for each editing session. Is there any way to have all fresh panels open on the smaller monitor please?

good day everyone! hoping to get some insight on a weird behavior i can't seem to figure out. i've tried affinity software off and on for a couple years now and have always seemed to have problems. i decided to bite the bullet and buy the latest release instead of trying the trial once a year to see if the issues subsided. they are still present (very slow, processes remain in memory after program closure, no pressure sensitivity, etc), but i'll deal with those once i get this behavior sorted. i am using a dual monitor set up. affinity photo remains in one window (my primary) and i have no need to break it apart into separate windows. i use an intuos pro tablet instead of a mouse. i use a button on my pen to switch be tween monitors. the problem is this: when i switch to another monitor, or essentially move away from the AP window without focusing on another window, the cursor starts wigging out and cannot center properly in the window, nor behaves properly within the AP canvas. here is a video that sort of demonstrates what is happening: https://www.youtube.com/watch?v=U2Gy0mzxJ-0 once i create a new document, you will see the cursor jump sporadically and flicker at times. this is me navigating to my other monitor and back to this one. i don't know if there's a setting i'm missing, either in wacom or affinity, that is causing this behavior. all drivers are up to date, and this is the only program on my computer that is showing this behavior. any thoughts as to what might be going on?