Compliments - Multi Line not working?

sdetweil

@noisedoctor I do not know. I don’t see how it ever worked. The field used does not interpolate the text. Just presents it as is.

I opened an issue, and logged the correction as a regression somewhere along the way

noisedoctor

@sdetweil – thanks so much. I wanted to confirm before reporting as a defect, but I guess you did that for me :)

broberg

@sdetweil said in Compliments - Multi Line not working?:

@noisedoctor I do not know. I don’t see how it ever worked. The field used does not interpolate the text. Just presents it as is.

I opened an issue, and logged the correction as a regression somewhere along the way

The \n gets converted to a whitespace in the textNode. And then the css pre -code converts every whitespace to a row break. It works on my setup, and probably more. Why it doesn’t on OPs setup is however beyond me.

sdetweil

@broberg said in Compliments - Multi Line not working?:

The \n gets converted to a whitespace in the textNode

I see a \n presented on the screen. whenever there is a \n in the compliment string.
as in “Hey there\n sexy!”

using the backtics, are supposed to allow line continuation across muiltiple lines AND encode a hex 10 (nl) char. but what a pain.

var msg=Hey there sexy
(note that this doesn’t show here on the forum either.)

it MAY be that the actual newline has to be encoded , NOT the text representation of the newline

 ('\n')

the default compliment text strings contains whitespace, where are NOT converted to breaks. so I don’t understand

I don’t see any improvement in using the file approach, as its content rules are javascript source rules. not message by line or anything else.

to test, I did nothing except install MM and edit the built in messages to add \n (two characters) in various places

i see the pre-line class, and read the description, but still haven’t figured out which nl they are discussing.

kayakbabe

@sdetweil I figured out that your suggestions of encoding the new line worked for me.
So, instead of using
\n
which textNode was treating literally, I tried encoding it and using this
\u000A

so when I tried the following it looked just like I put it into my morecompliments.json

"roses are red\nviolets are blue\nand I need a line\nto start here anew "

then I tried
"roses are red\u000Aviolets are blue\u000Aand I need a line\u000Ato start here anew "

and it displayed like I wanted it to like so…

roses are red
violets are blue
and I need a line
to start here anew

perhaps this will help others.

sdetweil

@kayakbabe crazy. my code splits the line with

"\n"

the problem was this forum changing the quote from

'\n'

to
‘\n’
notice the curly quotes, those are bad