"11.2"), removing the " m" unit (text becomes "11.2"), then enter or click elsewhere, the text turns automatically into "11.2 m" and everything is fine. What’s more, the released update included bugs that would slow down and crash Lightroom (which Adobe quickly apologized for and fixed), and certain features of.
Other bug fixes and stability improvements.
#Lightroom 6.2 bugs pro
Adobe Lightroom - Photo Editor & Pro Camera V6.2.1. already "10.0 m") and I modify the number (ex. Home » Apps » Photography » Adobe Lightroom - Photo Editor & Pro Camera » 6.2.1. if the altitude edit box is not empty (eg. "11.2") without touching the existing " m" unit, then enter or click elsewhere, the looping messagebox appears already "10.0 m") and I modify the value (ex. already "10.0 m") and I click in the edit box to enter edit mode, then type enter or clock elsewhere to exit the edit mode (without modifying the existing text at all), the looping messagebox appears Id like to personally apologize for the quality of the Lightroom 6.2 release we shipped on Monday, Adobes. if the altitude edit box is not empty (eg. Adobe has officially apologized for the bug. "10.0 m" or "10" or "10 m" then enter, the text becomes "10.0 m" and there is no message box If the altitude edit box is empty and I type eg. The problem appears when I click in the altitude edit box, then type enter or click elsewhere to exit the edit mode : the looping modal message box pops-up and I can do nothing but killing the process.Īfter new trials I have more precise information: the problem seems to occur only when there is a pre-filled unit (" m") in the edit box : The softwares, Lightroom CC 2015.2.1 and Lightroom 6.2.1 can. "39,6 m" or "39.6 m" depending on the separator I choose in windows language settings). Users have been complaining of a bug in Adobe Lightroom CC that was causing crashes. the Import experience available prior to Lightroom 6.2 as described here. The value read from the picture file is displayed ok (ex. The original import workflow has been re-established and many a bug fixed. I have tried with decimal separator as '.' or ',' the problem is the same. I have no problem with latitude/longitude, only with altitude
0 kommentar(er)
