On 5/4/2016 4:07 PM, stephen barncard wrote:
> you know you can store an entire stack as a custom property INSIDE another
> stack, right?
Yup.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe an
On Wed, May 4, 2016 at 12:37 PM, Paul Dupuis wrote:
> Thank you Mark. It turns out that about 15 minutes ago we found another
> approach to what we need to do that doesn't need us to covert a stack to
> text and back again. Still, it has me thinking about possible future
> uses. Who knows.
>
yo
On 5/4/2016 2:46 PM, Mark Schonewille wrote:
> I have created DIFfersifier a long time ago. A few years ago, I added
> a way to export stacks to XML. It isn't difficult to do that, since
> you just list all the properties as XML. If I remember correctly, a
> few properties can be read but not set,
I have created DIFfersifier a long time ago. A few years ago, I added a
way to export stacks to XML. It isn't difficult to do that, since you
just list all the properties as XML. If I remember correctly, a few
properties can be read but not set, or perhaps there was another
problem. I never got
Does it need to be a single text file? My lcVCS project creates a directory.
Sent from my iPhone
> On 4 May 2016, at 10:29 PM, Paul Dupuis wrote:
>
> Some time back on this email list there were discussions about tool(s)
> to write a stack (mainstack, substacks, controls, images, and all their
Some time back on this email list there were discussions about tool(s)
to write a stack (mainstack, substacks, controls, images, and all their
standard and custom properties) out into a text file that could then be
run through another tool to recreate the stack exactly. I think I recall
that the pu
