It looks like you're new here. If you want to get involved, click one of these buttons!
{
(set: $aloe's morality to ($aloe's morality -1))
<span class="description">
(either:
"Aloe glares at its soil, menacingly",
"Aloe lets out a high pitched evil giggle")
</span>
}
Used like this:
Haha, yes, people ARE worthless!!
(display:"aloe-reaction-evil")
This compresses the spaces before and after each line, leaving three unwanted spaces before the reaction.
Comments
So.... bump?
The following two examples both result in The quick brown fox, note the inserted space character between quick and brown This is what is happening in sammyt (and maybe Noctifer) example, the single extra space character between the end of the first </tw-expression> tag and the start of the <span> tag, and between the same <span> tag and the second <tw-expression> tag are more than likely the result of the new-line symbols being converted into space characters.
I just did this real quick and the output of that was: Then I went into the lng_bodyDescription function and cleared away most of the new lines and got it down to Then for good measure I went in and within the { } I commented out all the new lines and white spaces manually.. And that's brought it down to Eh, anyway, minor annoyance for formatting pretty code along-side pretty-text but not a show-stopper or anything. If it is just a known issue then that's fine (far as my stuff goes anyway), can always manually or scripting-wise strip out newlines in my code for release-versions and just keep them for my own work. Just wasn't sure if I was using the proper / intended tool.
The second issue is if you want the white-space: normal property to be only applied to some content then your going to have to mark that content in a way that CSS can find it.
note: the choice to use either a <div> or a <span> depends on the content being returned by your (display:)
eg. You could then add a CSS rule like the following within your Story Stylesheet to only change the white-space property for that content: One further complication is that the {} feature has been changed in the 1.1.0 version of Harlowe and works differently, exactly how differently wont be known until it is released. lol
Hopefully the upcoming version's tweaks make this un-necessary rather than requiring a different fix.
Thanks greyelf, you totally rock!