-
30 Apr 2012 12:06 PM #1
Ext 4.1: Constructing a KeyNav always results in a deprecation warning in console
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 #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 34,107
- Vote Rating
- 453
Does this happen without the compat layer?
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
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 services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
Thank you for reporting this bug. We will make it our priority to review this report.


Reply With Quote