[ExtJS 4.2.0.663] Ext.ux.DataView.Draggable can not be used in more than one DataView

[ExtJS 4.2.0.663] Ext.ux.DataView.Draggable can not be used in more than one DataView

Ext.ux.DataView.Draggable can not be used in more than one DataView in Version 4.2.0.663.
Reason is that Ext.ux.DataView.Draggable is now implemented as mixin.
Generally this is a good idea, but the implementation stores instance specific data directly in the mixin object.
Therefore, if more than one class is using the mixin, this data is overwritten which leads to unwanted side-effects.

I changed the implementation so that this data is now stored in the instance of the class that uses the mixin. That way the mixin can be used in multiple dataviews at the same time.

This is also the behaviour you can find in other mixin-classes as Ext.form.Labelable

If I do this - I can drag all Items comes from my store.
So the right description for this bug is maybe:

DataView cannot use DnD because it is not possible to catch the DOM-Objects (like select('div.card') ) - it is only possible to select the component it self.

Solution suggestion:
I think we need an override-fix of afterRender-function to wait for items in DOM or
a change when afterRender-function is called by procession rendering phase.

Wishes:
In my opinion it is also a design question related to loading multiple items you are waiting for.
So I would prefer an option makes it possible to POST-load content inner Draggable DOM-Item (lazyLoadItemChilds=true).
So we can come up and do not wait for Images for example - but draggability is working fast.

I am also thinking about the children of the DragZone:
I can see them if I do console.log(Ext.get(this.el.id).select('')) and follow elements[0]->childNodes or children
elements[0] is an HTMLDivElement

ext-all-debug.js:10317 TypeError: 'null' is not an object (evaluating 'dom.addEventListener')

So I think they are rendered outside of DataView Rendering-Phase what means the BugFix is also related to Ext.view.View and maybe it is really effecting other parts of this Component. But this is absolute over my level of experience. Here I will stop trying to figure out a usable workaround.

The basic problems others could stumble over could be:
1) Data-Source: You can use a Store as data-param

2) How to find out and point onto right Values: Console.log(store..); navigate data->items->[0..]->data
for example you want the id you have to use {[values.data.id]} into the tpl (please notice both brackets [] and {})