INTERACT FORUM

More => Old Versions => Media Center 16 (Development Ended) => Topic started by: jmcafee on March 11, 2011, 08:31:37 pm

Title: Find and Replace fills tag with the literal Expression string, not the result
Post by: jmcafee on March 11, 2011, 08:31:37 pm

In MC 16.049...

For my images I am trying to replace contents of the Album tag with [filename (path)]. In other words, "OFFICE\\Pictures\..."

If I use Library Tools/Find and Replace, the expression in the 'Replace' field is literally copied to the Album tag: "=[filename (path)]" (similar result if '=filepath()' is used).

However, if the same expression is directly entered into the tag, the path is correctly substituted.

Although I know for this particular example that I could achieve the same result using Copy Fields for the 'Filename (path)' tag, the issue points to a more fundamental question:  How to use any expression to fill a tag using Find and Replace?

Title: Re: Find and Replace fills tag with the literal Expression string, not the result
Post by: Matt on March 11, 2011, 09:08:34 pm

Find & Replace doesn't support expressions.  It might be a nice addition.

For now, you should be able to do the same by in-place editing or using the Tag Window.  Like a spreadsheet program, start with = to enter an expression.

Title: Re: Find and Replace fills tag with the literal Expression string, not the result
Post by: jmcafee on March 12, 2011, 02:12:52 am

Thanks, Matt.

MC is an amazingly robust program supported by a rich backbone of programability. I'm actually shocked that expressions are not used in Find and Replace since expressions are so ubiquitous elsewhere, and this seems like another natural use for it.

Title: Re: Find and Replace fills tag with the literal Expression string, not the result
Post by: fitbrit on May 12, 2011, 12:22:37 am

Quote from: jmcafee on March 12, 2011, 02:12:52 am

Thanks, Matt.

MC is an amazingly robust program supported by a rich backbone of programability. I'm actually shocked that expressions are not used in Find and Replace since expressions are so ubiquitous elsewhere, and this seems like another natural use for it.

+1 I was surprised at this too, but it was a long time ago. I just assumed it was my failure to do it right. So... a bump for this idea.