Lightroom SDK: CC 2015.4 broke edit_field's validate function, disabling existing plugins

  • 11
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
LR CC 2015.4 broke the validate() functionality of viewFactory:edit_field() on OS X 10.11.2, but not on Windows 10. This renders my Any Tag plugin inoperable for all of its Mac users.

Below is a script demonstrating the bug. On CC 2015.3 / OS X and on CC 2014.4 / Windows 10, when you type "abc" into the edit field and then hit tab, the validate() function replaces the contents of the field with the uppercase "ABC".  But with 2015.4 / OS X, the validate() function is never called, and the contents are not uppercased.  

Here are screenshots showing before and after tab is typed on 2015.3:




And here are screenshots showing before and after tab is typed on 2015.4:




local LrBinding = import 'LrBinding'
local LrDialogs = import 'LrDialogs'
local LrFunctionContext = import 'LrFunctionContext'
local LrStringUtils = import 'LrStringUtils'
local LrView = import 'LrView'
local bind = LrView.bind
local f = LrView.osFactory()
LrFunctionContext.callWithContext ("test", function (context)
    local prop = LrBinding.makePropertyTable (context)
    local result = LrDialogs.presentModalDialog {
        title = "validate test", 
        contents = f:edit_field {bind_to_object = prop,
            immediate = true, 
            value = bind ("value"),
            validate = function (view, value)
                return true, LrStringUtils.upper (value), nil
                end}}
    LrDialogs.message ("Contents of edit_field", prop.value)
    end)
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
  • Frustrated

Posted 4 years ago

  • 11
Photo of Michael Pollack

Michael Pollack

  • 7 Posts
  • 0 Reply Likes
Please fix this bug, Adobe. It breaks a plug-in that I have paid for and that I rely on.
Photo of Michael Anderes

Michael Anderes

  • 4 Posts
  • 1 Reply Like
Please fix this bug as fast as possible. I rely every day on this plugin.
Photo of Christian C. Berclaz

Christian C. Berclaz

  • 2 Posts
  • 2 Reply Likes
Adobe please do fix this bug as fast as possible as I heavily rely on this plugin!

Note that this reliance is caused by the unwillingness (is it inability?) of Adobe to add these elementary keyword functionalities to Lightroom itself. I find particularly irritating that a bug introduced by Adobe now breaks this very plugin.
Photo of robgendreau

robgendreau

  • 75 Posts
  • 20 Reply Likes
Aaargh. I thought it was me; thanks for catching this. PUHLEEZE fix it; I rely on plugins to keyword photos in the Map module since Adobe doesn't provide that function.
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
Be sure to vote for the topic as well!
Photo of bohdanz

bohdanz

  • 1 Post
  • 0 Reply Likes
I rely on Any Tag and it's upsetting that this update has made it impossible to use. Adobe, please fix this bug!
Photo of Gena Chattin

Gena Chattin

  • 1 Post
  • 0 Reply Likes
Cosigned. This plugin is vital since the keyword functionality native to Lightroom is pretty limited, and Lightroom is much less useful to us without it. We use AnyTag all day every day.
Photo of Steven Lippitt

Steven Lippitt

  • 4 Posts
  • 0 Reply Likes
Adobe, please do fix this bug a.s.a.p as I too rely on the AnyTag plugin!
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
Please vote on the topic as well.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2673 Posts
  • 348 Reply Likes
What happens if you just type in uppercase text?
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
"What happens if you just type in uppercase text?"

In the test program, it stays in upper case, which would be expected whether or not the validate() function is being called.  
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2673 Posts
  • 348 Reply Likes
In your plug-in(s) what happens without validate() working?
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
When it works properly, the user can type "j e<tab>" and that input will be replaced by the first matching keyword, e.g. "john r. ellis".  But when it isn't working properly, the input isn't replaced with anything, defeating the main purpose of Any Tag.
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 428 Posts
  • 150 Reply Likes
Hi,
We could reproduce this issue. We are looking into it.

Thanks,
Sunil
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
Great, thanks.
Photo of Morten Lien

Morten Lien

  • 1 Post
  • 0 Reply Likes
Any update on this? I rely heavily on John R. Ellis' excellent plugin in my workflow, and hesitate to update to LR CC 2015.4 before the issue is fixed.
Photo of camner

camner

  • 6 Posts
  • 0 Reply Likes
I'd like to add my vote to having this fixed asap....Any Tag is a very useful plugin that so elegantly extends the LR feature set.
Photo of Louis Sherwin

Louis Sherwin

  • 147 Posts
  • 34 Reply Likes
I use the plug-in for almost all my keyword input. It is terribly inconvenient with this bug. 
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
This bug appears to be fixed in CC 2015.5 / 6.5.
Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 428 Posts
  • 150 Reply Likes
Official Response
We have fixed this issue in the latest CC 2015.5 / 6.5 update.

Thanks,
Sunil
Photo of John R. Ellis

John R. Ellis, Champion

  • 4562 Posts
  • 1221 Reply Likes
Thanks for the update.  I've confirmed with my plugin that it works again too.