Thanks for explanation. So if I have set a column to be non-editable and I create a custom behavior for it, it will become editable? How about if the datagrid itself has been set to be non-editable? Just trying to get a handle on this since I couldn't find anything in the datagrid docs about it.
Maybe it's the way I use datagrids but I can't think of a single situation I have come across where I did not want a column containing a field to be aligned according to its column alignment. In fact, I have option menus and checkboxes that I really want to be aligned according to the column's alignment property and ended up writing code to make that happen. In other words, at least for me, ignoring the column alignment property should be the exception, not the rule. It makes things even more confusing that the inspector for the column still shows the original alignment property even though it's not observed. Personally, I would prefer that the inspector alignment option included an "undefined" ,or something similar, option to deal with these circumstances. Pete Molly's Revenge <http://www.mollysrevenge.com> On Tue, Sep 20, 2011 at 2:52 PM, zryip theSlug <zryip.thes...@gmail.com>wrote: > On Tue, Sep 20, 2011 at 9:19 PM, Pete <p...@mollysrevenge.com> wrote: > > Thanks zryip, that does fix the problem. But I have to say that it seems > > really cumbersome to have to do this. Does it apply to any properties of > > the column? > > Hi Pete, > > - The dgColumnAlignment is a column property which directly affected a > control in the default template for a datagrid. It is an equivalent > for setting the alignment property of the template field. > - The second is the dgColumnEditable property which allows or not the > edition of the default template field. > > The way for customizing the template and the column behavior script, > offers great possibilities to developers, far away that managing a > simple field in the column. If one customizes a column, the datagrid > library just assumes one have replaced the default template field by 1 > or several controls. So, the developers have and can manage those > controls the way they want, for example: > - by setting the alignment of the control (the field or whatever other > control we could have added in the template) > - by setting the effect they want for a non-editable column: lock the > field, disable a menu button or button, etc. > > > Best regards, > -- > -Zryip TheSlug- wish you the best! 8) > http://www.aslugontheroad.co.cc > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
