How to preserving XML tag string formats in variables?

Jim Ault jimaultwins at yahoo.com
Sat May 21 12:27:05 EDT 2011


Another hint for those who are good with custom properties...

Custom property sets are just arrays.

set the custompropertyset of this stack to "cpsXmlStrings"
set the customproperties of this stack to stringsArray
-- works with multi-dimensional arrays, but the keys and data cannot  
be accessed directly
--  however, the data is stored nicely and can be retrieved

or

put the customproperties of this stack into stringsArray
combine stringsArray using cr and tab  --no longer an array
filter stringsArray with "*<album>*"


Jim Ault
Las Vegas

On May 21, 2011, at 8:59 AM, Keith Clarke wrote:

> ...ah, thanks for the insights Jim. I have happily been using the  
> theHTMLText of fields to format text, set imagsource, etc. but  
> hadn't made the connection that fields would automatically interpret  
> any (some) tags. Obvious really - but everything is in hindsight! ;-)
>
> I use TextWrangler but it seems that custom properties are also  
> plain-text compatible - I'm using them to store the XML templates,  
> into which I replace placeholder lines. So, to save having to deal  
> with copy/paste or saving off to files for debugging, I now a cTest  
> custom property on the stack that I set and refresh to check plain  
> text, instead of using put or answer (as answer dialogues show the  
> same 'interpretive' behaviour).
>
> So, problem solved and another gem of wisdom stored away - many  
> thanks!
> Keith..
>








More information about the use-livecode mailing list