dreadnaxt
9 Nov 2011, 9:42 AM
Hello!
I'm working on DnD tree. To populate store i'm using loader which makes calls to the RPC service. The service retrieves data from the database using Groovy service.
Before, when I was moving the expandable node (i mean the node which has children), if it was already loaded (store contains BeanModel of this node) it stayed loaded. So when I was expanding it after drop the data was taken from the store cache. It was fine for me.
But now, when i drop the expandable node even if it's already loaded, after drop if i click on expand, the store calls the loader and so retrieves the data from DB, so i'm getting differences between BeanModel data of this node and the rest store data. For example imagine that node A has 2 children, B and C. I move child C to a new parent (let's call it node N). And then i move node A to a new parent also. When i expand it, i can see, that child C acting like it's still belongs to node A, but herewith it's situated in a different place in tree panel.
As i can see it happened after upgrading to the version 2.2.5 from 2.2.4, can anyone approve this problem? Or maybe share some workaround?
I'm working on DnD tree. To populate store i'm using loader which makes calls to the RPC service. The service retrieves data from the database using Groovy service.
Before, when I was moving the expandable node (i mean the node which has children), if it was already loaded (store contains BeanModel of this node) it stayed loaded. So when I was expanding it after drop the data was taken from the store cache. It was fine for me.
But now, when i drop the expandable node even if it's already loaded, after drop if i click on expand, the store calls the loader and so retrieves the data from DB, so i'm getting differences between BeanModel data of this node and the rest store data. For example imagine that node A has 2 children, B and C. I move child C to a new parent (let's call it node N). And then i move node A to a new parent also. When i expand it, i can see, that child C acting like it's still belongs to node A, but herewith it's situated in a different place in tree panel.
As i can see it happened after upgrading to the version 2.2.5 from 2.2.4, can anyone approve this problem? Or maybe share some workaround?