htmlText oddity

[Mark Schonewille]

Hi Craig,

I can very well imagine that this, and quite a few other esoteric peculiarities, drive you and other people nuts. Not everything is intuitive in LiveCode. (Another example of this is that the behavior of a control can only be set to the long id of a button, not to any other valid reference or to the long id of other controls).

At least it has been documented in the LiveCode dictionary. Probably, it must be a pair of <p> tags because the htmlText property of a field always starts with <p> and finishes with </p> and it must have seemed logical to Scott Raney to use this characteristic to determine if any text is htmlText.

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553

Use Color Converter to convert CMYK, RGB, RAL, XYZ, H.Lab and other colour spaces. http://www.color-converter.com

We have time for new software development projects. Contact me for a quote.



On 5 nov 2012, at 01:32, dunbarx at aol.com wrote:

> Mark.
> 
> 
> I read about "answer" in the dictionary, and found:
> 
> 
> 
> The prompt can be either formatted text (in the htmlText property's format) or plain text. If the prompt contains p or a start/end tag pair, the answer command  text is in the same format as the htmlText Property Otherwise, the answer command assumes the text is plain text.
> 
> 
> Not sure I fully understand this, but I bet it means I don't have to add a user note to the "answer" entry.
> 
> 
> But why only "<p>"? And further, if you substitute "<b>" for ","<p>", the answer command replies faithfully, in spite of the "contains p or a start/end tag pair" comment above, which it seems should include all such constructs, like "<b>". Isn't that a "start/end tag pair?
> 
> 
> This is the sort of thing that could drive one nuts trying to clean up persistent errors in code. 
> 
> 
> Craig
>