![]() ![]() I'm sorry but I'm not having any joy with your suggestion. I can't see anything else freely available which would produce a better result than the 2 options/versions I've now constructed. It rather trashes what o/w works perfectly. Perhaps it's the effect of the 2 initialise variables and/or the slice function at the point it's applied? ![]() If you have any idea about that I'd be grateful to learn of it!! I haven't a clue why this is happening, especially since I ensured there wasn't any such formatting on the blog message sent in the tests. However, you'll see from the pic of the delivered tweet on Twitter, the text is presenting as if formatted by a typing 'return', moving to prematurely to the next line. Given no element will vary in character number, it'll always work. In the twitter post body, I used the slice expression to limit the number of characters to, in this ex., 260, which delivers the post to Twitter within the 280 o/a character limit. The second one combines the collected tweet elements. First one is to collect what I want to limit the character numbers of. You'll see that I've utilised the "initialise variable" action twice. It saves quite a few character spaces & isn't essential as previously noted. ![]() I've been trying options out again & arrived at a working alternative but the actual Tweet is formatted undesirably!! Pics attached.įor this alternative I decided to leave out the Bitly url link back to the blog. ![]()
0 Comments
Leave a Reply. |