Could not open "filename" because there isn't enough room to display this document
- October 16, 2023
- 2 replies
- 902 views
Hello
This seems to be a recurring issue going back some time. Each time it was said that the issue was resolved with the latest update. I am currently using the latest version of Ps on an Intel Mac Pro and I am getting this warning so I will post this as a new issue should anyone else also be experiencing this error.
First, I was receiving these errors while using macOS Monterey. I also have seen the messages that Adobe would prefer that I use Ventura, macOS v13.
So I embarked on the upgrade journey. Before I did I removed Ps 2024 (v25) and Ps (Beta). I only left Ps 2023 (v24) on my system. I have now installed macOS Ventura v 13.6.
I downloaded and installed Ps 2024 (v25) and I have received the error "Could not open "filename.psd" because there isn't enough room to dock it on this monitor. Try turning off Open Documents as Tabs in the Workspace Preference panel. Which I did.
I tried again, only to receive the error "Could not open "filename.psd" because there isn't enough room to display this document. OK, so I created a new blank document 3000 x 2400 and made it a tab. I then went to the File>Open Recent and selected the same document that produced the error and it opened. It opened stand-alone, not as a tab. This file that generated the error is 6000 x 4000, a file size that never produced errors in Ps v24.
What I can't understand is why these errors now appear with v25 when they never appeared before with any previous versions and I am using the exact same monitors with the exact same configuration.
The main display is a Dell U4021QW set at 2560 x 1080 (Default). Should it matter, my second display is a Dell U2720Q set at 1920 x 1080.
All of my panels and toolbars are docked on the right side of my screen and once I open the offending document, all my tool interfaces are in exactly the position I expected them to be. Nothing is off the screen or on the second display.
So, as a non-technical person, I have reached the limit of what I know how to do. This is very frustrating and I hope that someone at Adobe will recognize the problem, offer a solution, and maybe fix this for the next update.
Thank you very much in advance.
