datagrid: sharing grid templates

Bob Sneidar bobs at
Wed Dec 15 12:43:41 EST 2010

Well this is interesting. I tried the method for determining the row template of a data grid that was copied from one stack to the other. Trevor is right, in that the pasted datagrid is using the template from the original stack! EEEK!!! 

If I close the original stack and remove it from memory and then try to edit the row template, I get a dialog called Save stack revPropertyPallette 1.livecode. This scares me. 

I would say then that the practice of copying a datagrid from one stack to another should be avoided at all costs. No telling what will happen now. 


On Dec 15, 2010, at 5:54 AM, Trevor DeVore wrote:

> On Tue, Dec 14, 2010 at 6:34 PM, slylabs13 <bobs at> wrote:
>> I don't think it works that way. If you copy/paste a data grid, I think
>> the
>> engine will also copy/paste the associated objects. Otherwise, copy/paste
>> of
>> datagrids could not work at all. For instance when you create a new data
>> grid, the button with the behavior script also gets created "behind the
>> scenes" otherwise the data grid would be dead in the water from the git go.
> If you copy and paste a data grid then only the data grid group is
> copied/pasted. That group will still point to the same templates as the data
> grid you copied. At this point the same templates are being used for 2
> different data grids.
> You can confirm this by checking the "row template" property of the data
> grid after copying. The property will return the same value for the original
> and the copied data grid.
> Ex: put the dgProps["row template"] of group "DataGrid 1"
> -- 
> Trevor DeVore
> Blue Mango Learning Systems
> ScreenSteps:
> Releasable Revolution Resources for Developers:
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list