Order of Child Items after drag /drop persistence

3 posts, 0 answers
  1. Rick Nguyen
    Rick Nguyen avatar
    21 posts
    Member since:
    May 2006

    Posted 01 Jul 2014 Link to this post


    I am using Kendo Tree View.

    I am doing drag/drop and I need to persist the info to the db. 
    Looking via the Kendo Plugin in Chrome.. I see  the  "4"  which was originally "1" after the move.  ( image attached)

    Example: also see image attached.
    4: Object{13}  //see via Kendo Plugin

    I was thinking I could get this  value  for the children under the parent where the items moved (example  0-4 ) and I can pair up the actual id with this index to figure out the sort order for children for persistence.

    Is there a way ... like in Grid which has index..... we can do the same in Treeview ?

  2. Atanas Korchev
    Atanas Korchev avatar
    8462 posts

    Posted 03 Jul 2014 Link to this post

    Hello Rick,

    Unfortunately I couldn't understand what you need.

    What value are you trying to get? Also what is this grid index that you mention? The grid widget doesn't have an index method.

    If you want to get the data item to which a tree node is bound you can use the dataItem method.

    Atanas Korchev

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. UI for ASP.NET AJAX banner
  4. Rick Nguyen
    Rick Nguyen avatar
    21 posts
    Member since:
    May 2006

    Posted 07 Jul 2014 Link to this post

    I found the solution.

    But the Object{x} I was noticing was the KendoUi deguging view in Chrome.

    Basically I was trying to see if the API had a way to give an indexed item array of all child items under a parent when you drag and drop an item  (over  parent ,,,after or before or over the child item).

    Kendo treeview has the  dropPosition  (over,before,after) and Target info which I was able to use to figure out where the dropped item need to be placed....  on the backend ..for persistence.


Back to Top