I'm thinking about maintaining row template cards, rather than the behaviors themselves - something very simple like (forgive the poor syntax)...
On create new group "new data grid", set the long ID of "new data grid's row template card" in stack "data grid templates <unique stack ID>" to the long ID of "new data grid" This would make the cards in the data grid templates stack meaningful without the developer having to remember the manual template naming detour. The ongoing tracking of changes to the long ID of the "new data grid" would be a nice to have, but this just seems to make sense for new data grids - as an option. Best, Keith.. On 23 May 2011, at 19:10, Bob Sneidar wrote: > A behavior script (which is what the datagrid template is) can have many > parents. In fact, every data grid you create by default uses the same > template unless you tell it to do otherwise. > > I am not sure what application there is for a custom datagrid template, since > you can intercept the messages that get sent to the datagrid template in the > script of the datagrid object itself, and then optionally pass the messages > later. > > This may be a question of method. > > Bob > > > On May 23, 2011, at 10:42 AM, Keith Clarke wrote: > >> Is it only me who would find it really useful to have the option to have >> data grid template cards automatically track the long ID of their 'parent' >> data grid? Maybe there are good reasons for not having them work that way, >> but manual house-keeping is something I like to avoid if possible. > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
