Lightroom 7.3: Dehaze adjustment opens up Effects panel when LrDevelopController.revealAdjustedControls is true

  • 4
  • Problem
  • Updated 8 months ago
  • Solved
  • (Edited)
The title says it all. This should be added to the list of bugs I've posted over the last few years.

Is anyone going to fix all the API bugs or are you abandoning the API? There's been no update in 3 years!

For example, see

Does anyone at Adobe care? There are lots of users of my free software (over 900 youtube videos discussing how to use it), but I'm thinking of pulling the plug if this lack of support and increasing number of bugs continues.
Photo of Rory Jaffe

Rory Jaffe

  • 37 Posts
  • 11 Reply Likes

Posted 2 years ago

  • 4
Photo of Stephen Soukup

Stephen Soukup

  • 23 Posts
  • 3 Reply Likes
Sad to hear. But if you scroll thru some of the problems list here you will see some of the problems are 5-6 yrs old and are still IN PROGRESS or only Acknowledged so... 3 yrs is nothing new it seems sadly. not acceptable. they need more QA and more employees to work on bugs it seems....
Photo of Paul Yarnall

Paul Yarnall

  • 15 Posts
  • 4 Reply Likes
This reply was created from a merged topic originally titled Dehaze slider and connection to basic panel still broken with external devices.

Latest update (4/24/18) did not fix the problem of using an external control (MIDI) for the Dehaze Slider still taking the panel to the Effects panel, where it no longer resides.  Please fix!!
Photo of Ganesh

Ganesh, Lightroom Engineer

  • 74 Posts
  • 23 Reply Likes
Thanks Rory for reporting this issue. We will work on this. 

Photo of Bhargav

Bhargav, Official Rep

  • 84 Posts
  • 20 Reply Likes
Official Response
Hi Rory Jaffe,

Thanks for reporting the issue.
We're working on a fix.
Photo of Paul Yarnall

Paul Yarnall

  • 15 Posts
  • 4 Reply Likes
I am not a coder, but some of these bugs should be a pretty simple fix. Looking forward to seeing them get "squashed"!
Photo of Rory Jaffe

Rory Jaffe

  • 17 Posts
  • 2 Reply Likes
Appears to be fixed in 8.3.1. Thanks.