When I've used a group as a document view, sometimes I just copy the group to
an invisible stackfile for storage.
The engine handles stackfiles efficiently and robustly.
If we had viewers it'd save me the copy step.
https://quality.livecode.com/show_bug.cgi?id=2786
Richard Gaskin
FourthWorld.co
Hey Bob, I just tested it and it captured the controls and properties and
custom property sets it would take extra work to "restore" a datagrid,
because we have to package the template stack.. but i think it will
work. Unless there is a property that the datagrid control has that is
unique
Including datagrids? I have a save and restore method for Datagrids, but I
don’t think I back up ALL the properties, just the critical ones.
Bob S
On May 20, 2024, at 5:58 PM, Tom Glod via use-livecode
wrote:
I have a plugin that is not complete which can save livecode groups and all
of thei
I have a plugin that is not complete which can save livecode groups and all
of their properties, custom properties and scripts. If you'd like I'll
send you some of the code. PM me.
Should be super easy to find the code u need, and then inverse it.
If you did that it would help me complete the plug
this is also how levure operates, so if you build with levure, you can just
do this with stacks in the project
On Thu, May 16, 2024 at 5:08 PM Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> You can save external stacks or created on the fly stacks where ever you
> have *wr
You can save external stacks or created on the fly stacks where ever you
have *write* (and read) permission on your OS.
Increasingly, whether macOS or Windows, that is not the Applications
(macOS) or Program Files/Program Files (x86) (Windows) folders. I find
the SAFEST place to save something
Craig,
Saving: the stacks within the MacOS package and the Windows Applications
folders can be saved—within that location?
Can new stacks/files be written to those same folders?
Peter
> On May 16, 2024, at 4:26 PM, Craig Newman via use-livecode
> wrote:
>
> I did not explicitly mention that
I did not explicitly mention that any and all of the attached stacks are
savable.
Craig
> On May 16, 2024, at 1:31 PM, Paul Dupuis via use-livecode
> wrote:
>
> On 5/16/2024 12:58 PM, Paul Dupuis via use-livecode wrote:
>> save that stack under a customer file extension
>
> That should have
There is much discussion about this on the forum.
The contents of the executable, the actual standalone you make from a stack,
cannot be saved by any OS. I use what is know as the “Splash Stack” method,
alluded to by Paul above.
In the Application Builder of the stack you are making the actual
On 5/16/2024 12:58 PM, Paul Dupuis via use-livecode wrote:
save that stack under a customer file extension
That should have said "custom file extension"
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, u
My suggestion would be to have your Standalone create a new stack with
the user's work and save that stack under a customer file extension for
your app.
You can not actually save data in a standalone. you must save it to some
source outside of the standalone - and stack, a text file, a binary
Hi list,
I am working on an app for a client who will use it as a standalone.
Basically users will be able to import data such as images, text and
even html from various sources. All these data will self organize in
different groups that the user will be able to select, move around
and organise in
12 matches
Mail list logo
