PDA

View Full Version : [OPEN] [#215] KeyNav/KeyBinding not working on TreePanel with TreeViewDragDrop plugin



martin.mosimann
Apr 22, 2013, 9:57 PM
Hi,

Since the update to release 2.2.0 the navigation by keyboard (up and down keys) as well as custom key bindings on TreePanels are not working anymore. The problem seems to be on every TreePanel where the TreeViewDragDrop plugin is used.

See examples:
http://examples2.ext.net/#/TreePanel/Basic/Custom_Drop_Logic/
http://examples2.ext.net/#/DragDrop/Tree/Tree_to_Div/
http://examples2.ext.net/#/TreePanel/Advanced/Remote_Mode/

Can you estimate know how long this will approximately take to be fixed and released as a new NuGet package?

Thanks for your support,
Martin

adrianot
Apr 22, 2013, 10:03 PM
Look at this link:
http://forums.ext.net/showthread.php?24518-ControlID-resolution-not-working-correctly-in-MVC-Web-Forms-mode-(-)

I had the same issue today, the fix is on SVN. Hope it helps,
Cheers!

Daniil
Apr 23, 2013, 6:29 AM
Hello,

@adrianot, thank you for the attention! Though, I am afraid it is another bug.

It turns out that it is a backside effect of fixing another bug.
https://github.com/extnet/Ext.NET/issues/178

To revert the changes back, you should add the following script on the page.

Ext.grid.plugin.DragDrop.override({
init : function(view) {
view.on('render', this.onViewRender, this, {single: true});
}
});

Ext.tree.plugin.TreeViewDragDrop.override({
init : function(view) {
view.on('render', this.onViewRender, this, {single: true});
}
});


Sure, scrollbar's jumps on selection will return back.

The problems with key navigation and a KeyMap is partially reproducible with pure ExtJS (I mean without the bug fix of a scrollbar's jumps). So, I reported it to Sencha.
http://www.sencha.com/forum/showthread.php?262006

martin.mosimann
Apr 23, 2013, 2:59 PM
Hi Daniil,

thanks for the quick reply and the workaround. This works absolutely fine. Keep up the great work!

Best Regards,
Martin

Daniil
Apr 24, 2013, 7:35 AM
Thank you for confirming.

Meantime, Sencha opened a bug ticket.

We created an Issue to track this defect.
https://github.com/extnet/Ext.NET/issues/215