LiveCode Forums.

That’s a useful approach, especially for tracking script changes across stack versions. Does your diff also handle object properties and UI changes, or mainly code differences?


I’m working on something that could be used to track other changes besides scripts. I have not added tracking yet to ...

I posted in that other thread too but thought it good to drop a link here. I wrote a stack that will export most everything out of a stack into mostly text files (images are binary of course). I have not created a repo for it yet but did run it over the HyperXTalk repo. Results here:
https://github ...

I've got two projects that may be useful in this context. The first (older) is ScriptTracker that just exports scripts of a stack as files:
https://github.com/bwmilby/scriptTracker
It does leave artifacts in the stack that it processes (a custom property set is added to each object with a script ...

Is this something where you could post a stripped down example stack? We would just need the loop piece and would not need to do any of the post processing of the received data. If it fails at the same spot in a test stack others can try it out and see if we get the same result.

It looks like you ...

Last I heard directly from LC is that the compiler is still planned to be released. Unfortunately without an updated advertised date it does leave those that funded it in an extended wait period.

One option would be to use a shared group that is placed on all cards. When the object is hidden it could be placed into this inventory group. When you unhide the item you would also need to move it out of the group. The way the shared group works would allow the image to be available on all cards.

You could iterate over the keys at the first level and get the size of each sub-array via encoding. Then you could do the same for the largest key at the next level and so on (if size would point to a possible issue).

Another option is to just use the tree widget to display the data and you can ...

Unless you have the stack password protected, I would use a tool to export the scripts of the stack out to files every time you make a commit on the binary. That would provide versioning of the scripts where you could easily see what changed over time.

Forums for Create:
https://discourse.livecode.com/

The forum was established for the Xavvi backers who were granted early access to test Create very early in development. I believe early access was also sold. The forum was initially for discussion of the new product and as a way for users to report bugs. From the LC bug comments I’m pretty sure they ...

Heather replied on the list that if you sign up for the webinar then you would be able to view a replay.

This was maddening.

One can set a custom prop to anything one wants. But one cannot set a custom prop to the contents of a variable with the same name:
snip
A new custom prop, named with the value of the variable itself , is created, and contains (what else?) the value of the variable. At ...

You could also layer another native control over the chart. I’ve seen examples before that used another browser widget with transparent background to overlay something over another native control. I’ll see if I can locate any of those examples.


EDIT: Here's a link to the post...
https://forums ...

It points up to the control. I was wondering if it should loop back and point down to the control (or even just back to the message path line).

OK, I think we're on the same page... just saying the same thing differently ;)

That being said... how would you like to see that inset graph changed?
the latest version seems fine to me, and not really saying anything different from what you say.

I agree, the flow for behaviors is a bit ...