metadata comma annoyance?

[Linh]

I'm getting a bit frustrated with Lightroom. I'm switching from Aperture to it mainly because I want something I can port over to windows if I end up w/ a dual OS environment, or simply go back to the PC world.

Anyway, when I'm entering keywords or captions, I've noticed when I hit the comma, it likes to auto-complete for me. With keywords, it sometimes will pick something else to finish off, eg, I enter "go," and as soon as I hit that comma, it will fill out as "good" My workaround is to hit space, then comma. As lightroom seems to adjust for trailing whitespace.

However, for captions, I might start out with "First," and once I hit comma, it fills out the rest of the caption with a previous caption that also began "First,"

It's quite annoying. Anyone else encountering this? I'm on the latest version of Lightroom and Leopard.

Thanks
Linh

 

[Gene McCullagh]

Linh,

I don't get that behaviour. LR presents it's suggestion for the completion of a keyword or caption. However, when you hit a comma the suggestion goes away. For example if I start to type me and LR suggests meadow and soon as I enter a comma after me the suggested adow disappears. The same happens in caption. It may be a Leopard issue. I am running on XP.

 

[Linh]

To bring this back to light... that is not exactly what I'm talking about. Again, I'm speaking from filling out the 'caption' field. Let's say I have the following phrase:
So, I went to the park

Now, I go to another picture, and I want to put in:
So, it was rained out

As soon as I hit the comma in this second picture, it will fill out with the line from the first picture. It's quite frustrating. However, I believe this is because it follows behavior for keywording, in that commas separate each keyword.

 

[Brad Snyder]

Try clearing the checkbox (if set) on

Edit > Catalog Settings > Metadata tab >Offer suggestions from recently .....

If that doesn't change the behavior, I don't know, beyond filing a bug/feature request. I can attest that most LR users have their individual pet peeves about the mechanics of the keywords/metadata entry fields.

 

[Kiwigeoff]

Linh, please do fill in a feature request as Brad suggested. I can sense the frustration and understand it 1''%:twisted:

 

[Denis Pagé]

To bring this back to light... that is not exactly what I'm talking about. Again, I'm speaking from filling out the 'caption' field. Let's say I have the following phrase:
So, I went to the park

Now, I go to another picture, and I want to put in:
So, it was rained out

As soon as I hit the comma in this second picture, it will fill out with the line from the first picture. It's quite frustrating. However, I believe this is because it follows behavior for keywording, in that commas separate each keyword.

Linh, I think it is more appropriate to use those sentences in the Title or Caption Metadata fields than in Keywords. For the keywords of those, just use "Rain" and/or "Park"...

 

[Brad Snyder]

Denis, if I read Linh's post correctly, I think he/she was referring to the behavior of the *caption* field, that is it was incorrectly parsing commas, and that it was behaving simlilarly to the keyword autofill. Which wasn't the desired behavior.

 

[Denis Pagé]

Denis, if I read Linh's post correctly, I think he/she was referring to the behavior of the *caption* field, that is it was incorrectly parsing commas, and that it was behaving simlilarly to the keyword autofill. Which wasn't the desired behavior.

Correct Brad, seem I missed his/her mention of captions...

 

[Mark Sirota]

Has anyone formally reported this bug?

 

[Brad Snyder]

Not I. Shall I?

Edit: Actually, now that I think about it, I was interested in what the OP had to say about turning off Auto Suggestion option in Prefs. If he/she responded, I didn't see it.

 

[Mark Sirota]

I think once that question gets resolved, someone ought to file it. And since you volunteered...

 

[Brad Snyder]

 

[Brad Snyder]

I've had a chance to play with this, and I don't think it's a bug. I don't think the comma has anything to do with it.

In the caption field, the behaviour I see is what I expect.

With auto-suggestions on, typing in the caption field will flash up a drop down list containing suggested captions matching the field entry so far. Commas seem to be just another character. I can choose one of those drop down suggestions, or continue typing to create a new different caption.

With auto-suggestions off, type whatever you want, no suggestions are displayed.

I think i need further clarification as to why Linh considers this a bug.

 

[Linh]

Wow, I hadn't realized this was updated... talk about years later.

The suggestion to disable auto-suggest works. I had thought that would kill it for keywords, but if it's in the database, it'll still come up.

The reason I think it's a bug is because hitting comma would automatically assume I wanted the rest of the suggestion. And I believe I was correct, since somewhere since then, this behavior has been fixed, heh.