Locked Columns using Angular

[Keith]

Hi

I'm using the angular directive for the TreeList and am seeing some strange behaviour when trying to set one or more locked columns. My column definitions are read from a database and returned to the client as an array :

[
{ field: 'col0',
  fieldName: 'Name',
  title: 'Name',
  locked: true,
  width: 240
},
{ field: 'col1',
  fieldName: 'ID',
  title: 'ID',
  hidden: true,
  width: 120
},

...

]

This array is then assigned to the config.columns property at which point the treelist is instantiated (via the k-ng-delay="widgetCtrl.gridConfig.columns").Unfortunately the locked property seems to be being ignored.

Strangely if I remove the locked property from the returned array and replace it with a hardcoded value:

restService.genericApi(self.widget.url + 'columns', false).queryPost(json).$promise.then(function (defns) {
                                                     _defn = defns[0];
                                                     _defn.columns[0].expandable = true;
                                                     _defn.columns[0].locked = true;

                                                     self.gridConfig.columns = _defn.columns;
                                                 }, function (error) {
                                                 });

This does lock the first column but then I have serious issues resizing: the locked column works ok. If I try to resize the 2nd column, the 5th one changes. It's the same all the way across (i.e. column which resizes is +3).

Is this a known issue​? and if so, is there a workaround?

Thanks

Keith

[Keith]

Update on this... the resizing issue is NOT related to locked column. It is because I have 3 hidden columns​. For example:

 

Column0 : Visible
Column1: Hidden
Column2: Hidden
Column3: Hidden
Column​4: Visible

..

[Dimo]

Hi Keith,

The resizing problem, which is caused by hidden columns was recently fixed and changes will take effect in the next internal Kendo UI build (usually we provide these on a weekly basis). Sorry for any inconvenience caused. A workaround is not available.

Regards,
Dimo
Telerik