Photoshop Subwindows open on wrong screen
- November 16, 2023
- 2 replies
- 697 views
This is a problem I reprted years ago and support promised me years ago that this will "soon" be fixed, but it is not fixed until today.
Photoshop Version: All versions
OS: Windows 10, latest patch
I have four monitors for multiple work related reasons. One of them is a pen tablet.
I work on Photoshop on my main 4K monitor most of the time.
Sometimes I want to use the Pen Tablet monitor.
If I move the main Photoshop Window to the Pen tablet, all child windows still open on the main monitor, not "inside" the Photoshop window. Since the Pen tablet monitor is two monitors to the left and at a 90 degrees from my main monitor (I rotate the chair to use it), I have to move all child screens from the main monitor to the pen tablet monitor.
The problem is: They stay there. If I want to use photoshop on the main monitor again, I again have to move ALL CHILD WINDOWS back to the main monitor.
Since you surely know how many child windows opens when working for it this is not acceptable and it takes A LOT OF TIME to do that. Also since the pen tablet monitor is not on all the time to save energy, sometimes I cannot eben see that there are PS child windows open on it.
As I said: I reported this years ago and had contact with multiple support representatives. The last one promised me "a fix soon!". I suggested a setting in options where I can set a checkmark that forces PS to open child windows on the main window.
That last promise was early in 2022. The german support representative wrote:
"Wie bereits beschrieben arbeiten wir an einer Lösung und bedaure, dass wir diese bisher nicht ausrollen konnten. Gerne informiere ich Sie schnellstmöglich, sobald mir dazu ein genauer Veröffentlichungs-Termin vorliegt."
Translation:
"As already described, we are working on a solution and regret that we have not yet been able to roll it out. I will be happy to inform you as soon as possible as soon as I have an exact release date."
Now, nearly two years later, nothing was fixed. This is another case where I experienced abysmally bad Adobe support.
