Hi, I'm using normal Jewel DataGrid for predicted basic scenarios (small amounts of data) with support for edition. I'm using Jewel VirtualDataGrid for predicted complex scenarios (query with many rows) and it's working (not perfect but working).
I have now a third need that it's a complex amount of data and the need for an edition, so I went through Jewel VirtualDataGrid but faced the problem that the keys are blocked. I discovered that the "guilty" was VirtualListKeyDownController class. VirtualDataGrid uses VirtualList and VirtualList use VirtualListKeyDownController. This class basically ignores tabs (to not lose focus) and does a preventDefault that doesn't allow me to type on my TextInput inside the VirtualDataGrid. I understand from the class commented code that the intended was to be able to navigate up and down but it's too complex in a virtual way to do at that time but preventDefault should not be the way. I did a patch on my side, removing the preventDefault and the VirtualDataGrid it's now working with editing like the normal DataGrid. I have now a lot of priorities on my Flex to Royale rewriting but in the near future if no one completes this class, I will probably try to allow the VirtualList and VirtualDataGrid navigate up and down with the keyboard. Did you guys agree to remove the preventDefault from the origin and commit it ? Regards, Hugo.
