Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[gappie]

i want to make an expression to copy keywords to the notes field. but all the keywords should be seperated by a return. everyone of them has its own line..

thanks
 
gab

[MrC]

I can't think of any way to introduce a newline into an expression.  Regex() stops at newlines, so we can't capture an embedded one.

Edit for strikeout above: Regex() does not stop at newline; rather, the flag Dot Matches Newline is unset, so it is not possible to use dot to capture a newline; this also implies that you cannot span lines using .* or .+.  Regex() does support \n escapes, so you can capture one of those directly:

   Regex([field with newline], #/(\n)#/, ...

MC should support \n and \r in output for large text fields, so that fields such as [Notes] can be built from other fields.

I think it should also support the flag for Regex() that allows Dot Matches Newlines; otherwise it is generally not possible to pull data across multiple lines in [Notes].

[MrC]

Solved!

I hadn't thought to test another way.

In a single Notes field, add a single newline (just hit return).  Take note of the record you are adding this to.  For example, perhaps it is a file with Name=FooBar

Add an expression column, or equivalent syntax in Set rules for file display, adding:

   if(isequal([Name],FooBar),save([Notes],newline),Ignored)

Now, for the file(s) you want to change, edit Notes and enter:

   =replace([keywords],;/ , [newline])

This grabs the single newline from the global variable newline and replaces the keywords semicolon/space delimiter with the newline.

[gappie]

brilliant! creative and crazy. i love it 

it works. i also tried regex stuff, but im not good in it, and im happy to hear that that was not the only problem. but never thought i could use a global variable for it, and in that way.
i think i can streamline it a bit for regular use.

thank you very much
 
gab

[MrC]

I've updated my comments above.  You can use Regex() to capture a newline.  It just has to be done specifically, rather than by using the match-any character dot.  The expression:

   Regex([field with newline], #/(\n)#/, 1)

will output a single newline, and capture [R1] can be used as well.

[gappie]

thank you again.. ofcourse i could not get it to work. its to late to think clear enough, i really need to get into this regex stuf. but tomorrow i will. today i found this \n on some site and tried. now i need to understand. i will get it.

thanks
 
gab

ps: your first solution i did understand, and works very nice. made it the way i wanted, and my viz studio thing starts to give the info i want and even to look nice..... it was a good mc-day.

[vagskal]

Does this mean that there is a way I could use new line in an expression field to be used in thumbnail text, i.e. to output new line and "something" only if there was "something" to output?

[MrC]

Does this mean that there is a way I could use new line in an expression field to be used in thumbnail text, i.e. to output new line and "something" only if there was "something" to output?

In Thumbnail text, when the newline comes from a field's value, it appears MC replaces the newline and everything after it with ... .

[vagskal]

Thanks for the replay.

In Thumbnail text, when the newline comes from a field's value, it appears MC replaces the newline and everything after it with ... .

Too bad. It was close though. I had not even figured out how to put new line in an expression field.

[marko]

Neat solution, very neat.

[MrC]

thank you again.. ofcourse i could not get it to work. its to late to think clear enough, i really need to get into this regex stuf. but tomorrow i will. today i found this \n on some site and tried. now i need to understand. i will get it.

The regex() I posted wasn't a complete solution, so it wouldn't work without the additional code.  It was a proof that a newline can be captured and later used.  To use it, you'd want to use this in some column:

   ifelse(regex([Notes],/#(\n)#/),save([R1],newline))

It won't produce any output, but does set the newline variable so long as some Notes field has a newline in it.  You could also perform it in the Set rules for files display with a custom rule:

    [=ifelse(regex([Notes],/#(\n)#/),save([R1],newline))1]=1

and this will make the newline value set for the view (no empty expression column necessary).  If you set this for the top level Audio view, all your child views will then have access to the pseudo-field [newline], and you can use it freely henceforth.