30 Apr 2012 12:06 PM #1
Ext 4.1: Constructing a KeyNav always results in a deprecation warning in console
I'm seeing this in 4.1.0. Apparently, there is no way to construct a KeyNav without generating a compatibility layer error. The logic in the compatibility layer that determines if an error should be logged is, well, bizarre to say the least. It's causing the following message to appear over and over again in my js console: "[DEPRECATED][4.0][KeyMap]: Ext.KeyMap has been deprecated, use Ext.util.KeyMap."
1 May 2012 7:39 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
Does this happen without the compat layer?Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.