10 Messages
•
294 Points
Sat, Sep 21, 2013 3:31 PM
Solved
Lightroom: 5.2 Update Adds Bug to exiting Full Screen Preview Mode
The Lightroom 5.2 update added a bug to the Full Screen Preview mode.
Previously, when in Full Screen Preview mode and you hit a quick key to enter a module (rather than exiting by hitting "F") it would simply exit the Full Screen Preview mode and enter said module without changing your screen mode, but now...
Now when I exit with "F" everything is fine, but if I exit with "Esc", "D", "G", or "E" then it takes me OUT of Full Screen and into Normal.
This is incredibly frustrating.
Previously, when in Full Screen Preview mode and you hit a quick key to enter a module (rather than exiting by hitting "F") it would simply exit the Full Screen Preview mode and enter said module without changing your screen mode, but now...
Now when I exit with "F" everything is fine, but if I exit with "Esc", "D", "G", or "E" then it takes me OUT of Full Screen and into Normal.
This is incredibly frustrating.
Problems
•
Updated
7 years ago
2
16
Helpful Widget
How can we improve?
Tags
52 update
bug
full screen preview
solved
Responses
Official Solution
michael_rork
10 Messages
•
294 Points
7 years ago
0
0
erik_underbjerg
1 Message
•
64 Points
7 years ago
I can confirm the behaviour Michael explains, with one addition: If I am in Full Screen mode, enters Full Screen Preview (by pressing F), and then rapidly presses the F key two times in a row, Lightroom also revert to "Normal" screen mode.
It's very fustrating.
0
0
luc_renambot
5 Messages
•
130 Points
7 years ago
0
0
jeff_charles_6065085
2 Messages
•
72 Points
7 years ago
0
0
jeff_charles_6065085
2 Messages
•
72 Points
7 years ago
0
0
londonyank
6 Messages
•
124 Points
7 years ago
My workflow has me switching very frequently between Grid and Fullscreen or Develop and Fullscreen and when I am in mid-workflow, I want Lightroom to remain in "full screen" window mode if that's what I specified when I return to Grid or Develop.
0
0
erik_underbjerg_6183015
2 Messages
•
78 Points
7 years ago
0
0
michael_rork
10 Messages
•
294 Points
7 years ago
0
0
der_dembo
5 Messages
•
112 Points
7 years ago
0
0
michael_rork
10 Messages
•
294 Points
7 years ago
0
0
michael_rork
10 Messages
•
294 Points
7 years ago
0
0
michael_rork
10 Messages
•
294 Points
7 years ago
0
0
john_thomas_6589788
6 Messages
•
184 Points
7 years ago
0
0
john_thomas_6589788
6 Messages
•
184 Points
7 years ago
0
0
erik_underbjerg_6183015
2 Messages
•
78 Points
7 years ago
The issue Michael Rork described was fixed for some of us in 5.4, albeit after a rather long wait.
I would suggest you open a separate issue for what you're experiencing.
0
0