Official

Accepted

Unanswered

Advanced Filters

Search Results (193)

Relevance

Closed

Lightroom SDK: publishService:getCollectionByLocalIdentifier

From a collection handling point of view, the catalog and publish services can be treated as collection sets - they both have the same methods for collection management. This is real nice, except: publish services lack the method to get a collection by local ID. Plug this one little hole and colle

Ideas

 • Lightroom Classic

8

0

2

Closed

Lightroom Classic: Lightroom ACR API

How can I get access to the below API? https://adobedocs.github.io/lightroom-api-docs/ In the Adobe Developer console I see the Lightroom / Camera Raw API is greyed our on the bottom right. Is this the API which is needed?

Question

 • Lightroom Classic

80

1

Closed

Lightroom SDK 5: LrBinding.andAllKeys and orAllKeys in conjunction with optional bind-to object param - doesn't work, or needs better doc..

LrBinding.andAllKeys( optObject, keys ) LrBinding.orAllKeys( optObject, keys ) 1. Documentation of 'keys' parameter is different for these - orAllKeys documentation should be amended to be same as andAllKeys, which is closer to correct. 2. Neither one works with the optional object parameter pass

Problems

 • Lightroom Classic

6

0

Closed

Lightroom: If a plugin is disabled, don't even load it, or at least don't execute its initialization module.

As it stands, even disabled plugins are loaded and initialized, and async tasks may be started and executing. As it stands, "disabled" means "custom metadata, menu items, tagsets, and export filters/services are hidden" - I'd rather "disabled" mean "completely disabled". Bonus idea - if an export i

Ideas

 • Lightroom Classic

5

0

1

Closed

Lightroom SDK: LrApplication.getPath() -- get path to Lr executable file

It would be helpful, e.g. when creating bat files which start or restart Lightroom, to know path to Lightroom. Tnks, R. It's easy enough to have field for user to edit, but then it needs to be fixed everytime user updates Lr version.

Ideas

 • Lightroom Classic

20

1

1

Closed

Lightroom SDK: A way to flush preferences from ram to disk.

As it stands, Lightroom saves preferences to persistent storage upon (normal) exit, which means if it crashes or is restarted then the preferences are not saved. How about a way to flush to disk before exiting. This would not only allow a plugin to assure its preferences are saved, but would also al

Ideas

 • Lightroom Classic

2

0

2

Closed

Lightroom 5 SDK: photo:createDevelopSnapshot( name, true ) -- creates duplicate snapshot if photo is virtual copy.

I believe this symptom is related to the fact that photo:getDevelopSnapshots() returns an empty array if photo is virtual copy, i.e. Lr is only recording develop snapshots for master, so snapshot created by virtual copy never seems like a duplicate. So, one needs to always have logic like this when

Problems

 • Lightroom Classic

10

0

Closed

Lightroom SDK: add method "reload" to LrDevelopPreset object, to reload settings from disk.

This would allow plugins to alter presets - without requiring a restart for changes to take effect. Also, features to: * create new user presets. * move/rename existing presets. * delete presets. etc. would be good. ~R.

Ideas

 • Lightroom Classic

10

0

2

Closed

Lightroom SDK 5: FTP logging is broken

From the api doc: ftpConnection.loggingEnabled : (Read/Write) (Boolean) True to enable logging. Retrieve the log and clear it using ftpConnection:getAndClearLog(). i.e. loggingEnabled should be a writable property. However, when attempting to write loggingEnabled property an error is thrown:

Problems

 • Lightroom Classic

6

0

Closed

Lightroom SDK: LrShell.openPathsViaCommandLine vs. LrTasks.execute - is there an underlying difference?

I always assumed LrShell.openPathsViaCommandLine was just a "front end" to LrTasks.execute, taking care of quotes and OS differences..., but after reading the documentation for LrShell.openPathsViaCommandLine, it sounds quite different from LrTasks.execute. Are they ultimately using the same "techno

Question

 • Lightroom Classic

8

0

Closed

Lightroom SDK: LrShell.openPathsViaCommandLine - doc says number returned, experience says boolean returned.

LrShell.openPathsViaCommandLine is returning true when it works, nil when it doesn't.

Problems

 • Lightroom Classic

6

0

Closed

Lightroom SDK: Like deprecation warning, let's have a backward compatibility warning.

Problem: sometimes users are the ones to hit the bugs in older versions of Lightroom (due to using newer SDK features), instead of plugin author. How about supporting another option in config.lua like you do for deprecation warnings, except for "backward compatibility" warning, for example, in conf

Ideas

 • Lightroom Classic

1

0

1

Closed

Lightroom (SDK) 4.3RC1: catalog:batchGetRawMetadata( photosAndVideos, nil ) -- error

This code was working, up through Lr4.2: catalog:batchGetRawMetadata( union ) -- nil should mean: all metadata. (note: union is a valid array of LrPhoto objects). but in Lr4.3RC1, that code results in an error: bad param #1 to ipairs - expected table, but is nil... - or something very close to th

Problems

 • 

Solved

 • Lightroom Classic

2

5

Closed

Lightroom 4.X SDK: Hopelist...

Hopefully, Adobe will be releasing the Lr 4 SDK soon. Although my expectations are low (call it a hunch), these are some minimum hopes: * The bug that keeps users of plugins with custom metadata from being able to upgrade (due to Lr catalog-update error *before* plugin update-schema function even

Ideas

 • Lightroom Classic

2

0

2

Closed

Lightroom: @Lr3.6RC tagset definitions are no longer sufficient for automatic plugin init.

Up through v3.5, there were two ways to assure a plugin started up with Lightroom (i.e. asynchrous initialization and/or background processing): 1. Metadata defined. 2. Tagset (even an empty one) defined. I've chosen to depend on #2 to avoid the "catalog must be updated" prompt that accompanies #

Problems

 • Lightroom Classic

1

0

Closed

Lightroom SDK: tooltips don't work in export dialog box

I thought they used to work, although my memory is hazy. In any case, I can't get tooltips to work at all in the export dialog box @Lr3.5 Lightroom version: 3.5 [775451] Operating system: Windows 7 Ultimate Edition Version: 6.1 [7601] Application architecture: x64 System architecture: x64 Phy

Problems

 • Lightroom Classic

6

1

Closed

Lightroom SDK: Fonts.

Please document which text fonts are built-in for use on which platform, and how to include a font with a plugin that would ensure the same look on both platforms, or even platform dependent fonts... e.g. for static_text Bonus Idea: --------------- - Include some fonts with Lightroom to be avail

Ideas

 • Lightroom Classic

4

1

3

Closed

Lightroom Feature Request List - Prioritized.

Some have suggested my priorities are unclear since I say "Good Idea / +1 vote" to a lot of things, even if they wouldn't be top priorities for me. So, to be clear: Develop Module: 1. Fix Highlight Recovery (does not work well with twisted profiles. Flat -n pink springs to mind...) 2. Smo

Ideas

 • Lightroom Classic

11

1

3

Closed

Lightroom SDK: shared widths are dialog-box-wide, so one plugin's shared widths may screw up another's layout.

shared widths are dialog-box-wide, so one plugin's shared widths may screw up anothers layout. e.g. if I write width = LrView.share( 'my_width' ) and another plugin sharing the dialog box (e.g. export filter) also has width = LrView.share( 'my_width' ) then both plugins will have width of compo

Problems

 • Lightroom Classic

5

0

Closed

Lightroom API Bug with Cropmode for panoramic watermarked images

Lightroom API Bug - happens in all version When using the following settings, ["photoSizes.thumb.cropMode"] = "minimum", with watermarks enabled on thumbnail images over 150px which the original photo is panoramic in ratio for example 4000px by 1000px. Lightroom crashes when creating the images,

Problems

 • Lightroom Classic

0

0