Thank you for reporting this bug. We will make it our priority to review this report.
-
27 Sep 2012, 12:29 AM
#471
Ext Premium Member
http://docs.sencha.com/ext-js/4-1/so...thod-deprecate
The documentation and example say that the argument "4.0.0beta" would perform the code even when the current version is "4.0.0beta". But actually, the code checks if the version comparsion is smaller than 1. This means, that the code will not performed if the current version is 4.0.0beta
So, the documentation should say: Specify the version in which the function won't be called.
Maybe, this is issued by the build number (Ext.Version.compare(Ext.getVersion('extjs'), '4.1.2.1') == 0. Should this be correct?
My replay:
Ext.getVersion('extjs')
Ext.Version.Ext.extend.constructor
- build: 1
- major: 4
- minor: 1
- patch: 2
- shortVersion: "4121"
- version: "4.1.2.1"
- __proto__: F
Ext.Version.compare(Ext.getVersion('extjs'), '4.1.0')
1
Ext.Version.compare(Ext.getVersion('extjs'), '4.1.1')
1
Ext.Version.compare(Ext.getVersion('extjs'), '4.1.2')
1
Ext.Version.compare(Ext.getVersion('extjs'), '4.1.3')
-1
-
27 Sep 2012, 12:54 AM
#472
@Jan: yes, the build number is taken into account when comparing versions. So that 4.1.2 < 4.1.2.1.
-
27 Sep 2012, 1:42 AM
#473
Ext Premium Member
Hm, okay. But the build number is a new property? What about some generics, like "~", "*" or "?"? I.e. for a usage like "always 4.1.2 regardless build"?
Anyway, imho the build number should be taken account in the documentation.
-
29 Sep 2012, 1:02 AM
#474
Sencha User
There is no information about store.autoDestroy
The documentation does not have enough information about Ext.data.Store.autoDestroy, which is used in Ext.util.Bindable.bindStore().
After destruction of the grid, the store is not destroyed automatically. If not used storeManager (if the store is created without the storeId) and not to destroy store manually, then store remains in the memory.
Maybe later it will be deleted memory manager, but for this purpose there is a Ext.data.Store.destroyStore().
If you add autoDestroy = true, on destruction of the grid is automatically called store.destroyStore(), which destroys store (cleans it, removes the listeners, etc.).
-
30 Sep 2012, 11:46 PM
#475
Ext.ModelManager
IMO instead of "The id of the model or the model instance" should be "The class name of the model" or sth like this. How it is, sounds confusing, I was looking for some id, but when I looked to code I understood that the argument value can be only the class name of the model.
-
30 Sep 2012, 11:56 PM
#476
Also those code lines in that class, at the top of page, don't work, at least at me, the getModel() code confirms that below example returns undefined not usertype:
EDIT:
Seems an extjs bug, because, when defining a store , there's 'model' config where docs says
model : String5
Name of the Model associated with this store. The string is used as an argument for Ext.ModelManager.getModel.
looked in code and indeed ModelManager.getModel is used. So if I use in store:
- model: 'User' , won't work
- model: 'AppNamespace.model.User' works.
-
12 Nov 2012, 8:37 PM
#477
Sencha Premium Member
ExtJS 4.1.3 - Documentation Bug - Link not working
Folks,
Link to the document mentioned here ( Inside KeyMap Section - http://docs.sencha.com/ext-js/4-1/#!/guide/keyboard_nav ) that maps which numbers correlate to which keys is dead!
"404 Not Found Error"
http://docs.sencha.com/ext-js/4-1/ext-js/4-0/source/EventObject.html
Thanks
-
Sencha User
http://docs.sencha.com/ext-js/4-1/#!/api/Ext.data.Store-method-sum
"Ext.data.Store
Sums the value of property for each record between start and end and returns the result. **
... "
"Property", "start", and "end" aren't mentioned in the entry, nor in the code. If they do apply to the entry, some specification is desired.
-
Thanks. All the above issues have been fixed internally.
-
10 Jan 2013, 3:06 PM
#480
Sencha User
RegExp symbol text error
The following text shows up in RegExp, near the middle.
`x y | Mathes eitherxory`.
It looks like a tic mark was left off.