Skip to main content
Kukurykus
Legend
February 28, 2018

P: There isn't enough room to display this document

  • February 28, 2018
  • 61 replies
  • 1207 views

https://forums.adobe.com/thread/2458817

I read all topics about this problem and tried all solutions. Some helped but only in specific scenarios they are no options for me. There was not mentioned (at least for me) REAL cause of this error so I am creating new topic. I hope it is more helpful...

All proposed default Ps workspaces have tools panels docked to left margin of screen. It is why they let you to open files in normal size. When you dock your Tools panel to right margin of screen all is okey too. Any panel, however docked or not to any other or margin does not make difference. All works still good. Problem occurs only when you undock your Tools panel from left/right margin of screen. If you move it few centimeters from left margin all is still fine, but always when you move it farer to right side of screen (and from up) an created/opened document will minimalize its size due to Tools panel distance from left screen margin. If additionally you dock your Tools panel to any other panel that is not docked to left/right margin of screen (but moved to specific location in your Ps workspace) error is going to occur while creating/opening document.

This is of course bug! The only I can do is to turn off Tools panel what is ridicolous solution or else dock it to right Ps screen margin what doesn't satisfy me too for reason It covers too much space along with other panels I keep as small as possible.

This is my first day with CC 19.1. So far i used CS6 for few years. From that I read prior CC versions doesn't have this bug yet.

Since I use specific panels location I can't work with this bug. I'm going to use CS6 until next CC update that fix this problem.



That's really funny first action, opening file I did in newest Ps after relocating panels (including Tools) ended up with error 🙂

This topic has been closed for replies.

61 replies

Kukurykus
KukurykusAuthor
Legend
May 15, 2018
After 3 months if finally works again!
Hannah Nicollet
Community Manager
Community Manager
May 15, 2018
Woot!
Pete.Green
Community Manager
May 15, 2018
This issue should be fixed in the Photoshop CC 2018 (19.1.4) release which is now available. 

Please update Photoshop CC 2018 via the Creative Cloud desktop app and let us know how it goes for you!
https://helpx.adobe.com/creative-cloud/help/update-app.html

Regards,
Pete
Kukurykus
KukurykusAuthor
Legend
May 2, 2018
What others say who experience this problem but for reason of using 'dual monitor system' docking Tools Bar doesn't help. Bob Roby didn't say how it's for him, but probably it won't help him too. It's why in other post of this theard I suggested to merge it with other topic, dedicated to his issue.
Kukurykus
KukurykusAuthor
Legend
May 2, 2018
That new topic of Bob Roby shouldn't be merged with this one. It's the same problem but caused by dual monitor system. In this case it should be merged with proper topic, so this one:

https://feedback.photoshop.com/photoshop_family/topics/cc-2018-win-10-images-opening-unexpectedly-sm...
Legend
May 2, 2018
FWIW - a workaround is either dock or hide the Tool bar.
Participant
May 1, 2018
Thanks for the update. The problem is not serious but it is disconcerting.
Legend
May 1, 2018
This problem is the result of the same root issue on this thread. It will be fixed in the next update. We will update this thread when the update is released.
Participant
May 1, 2018


I have the same issue on a current win 10 dual monitor system. Images are opened at about 8% of full size. This didn't start until I installed the 19.1.3 release of PSCC. 
Kukurykus
KukurykusAuthor
Legend
May 1, 2018
I believe they work hard now on next update that possibly will be last one for CC 2018 release. As there are no serious problems to use Photoshop now (not for me though) perhaps they can focus with no pressure on every single one that came with 19.x version and was found by users. If so and unless this and other fixes won't affect wrongly on anything there works properly already we can expect no more updates 🙂

It's about month elapsed from 19.1.3, so probably this bug will be gone very soon, however I'd like to wait even one month more if all others had to be sorted out too thanks to this additional time...