Saving datagrids Solved
dunbarx at aol.com
dunbarx at aol.com
Sat Feb 19 14:56:19 EST 2011
Thanks, Adding the library fixed it. Whew.
I did not receive this stack in the standard download of LiveCode 4.5. I got it from Blue Mango Software.
The application builder could not find it. In fact, I have to add it by hand in the settings, whereas the lesson on making a standalone
with a DG indicates this should happen automatically. Anyone else run into this?
Thank you again, and all who tried to help.
From: zryip theSlug <zryip.theslug at gmail.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Sat, Feb 19, 2011 12:39 pm
Subject: Re: Saving datagrids
On Sat, Feb 19, 2011 at 5:47 PM, <dunbarx at aol.com> wrote:
> My working stack is a substack of the splash screen stack. The standalone
builder has included a datagrid templates stack in the stack files. It always
did. May I assume this is the library stack you mentioned?
The template substack and the library are two completely differents things.
Lets me clarify this a bit:
1. The template substack
The template of a datagrid contains the description of the objects
inside the different columns (for the datagrid table) or the objects
in a datagrid form.
For a datagrid table the template of the datagrid contains a group by column.
For a datagrid form the template contains only a group that we can
consider as a template row.
Defaults objects in a template are
- a background used to fake the hilited state of the row
- default container : fields
You can customizing the template of the datagrid by adding every type
of objects you want: a button, a checkbox, an image, etc
For building the datagrid, the datagrid engine replicates the template
for each (visible) row it has to draw.
The template substack is composed by a background card (the one which
content some explanation how editing the datagrid template) and a card
for each datagrid includes in a project.
Each datagrid have a property containing the link with it's template card.
Note that for a datagrid table, the template is facultative, if you
have not to customize it.
2. The datagrid library (also named datagrid engine in this description)
Each part of a datagrid group (the header, the rows, the scrollbar,
etc) is linked to a corresponding parent script in the library.
Each property you use with a datagrid is a virtual property (the
dgText, dgData, etc) resident in the engine and linked to the datagrid
group by a parent script.
The library of the datagrid is located in the revdatagridlibrary stack.
If the library missing, the parent script is not resolved and no
virtual property will intercept your code. Setting the dgText or
dgData of the datagrid group will behave same the lock message is set
to true: the properties will be added physically in the group, instead
to be intercepted by the virtual properties (setProp, getProp) of the
If you try to use your car without the engine, the things should be a
bit difficult. This is same with a datagrid if the datagrid library
-Zryip TheSlug- wish you the best! 8)
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
More information about the Use-livecode