-
23 Aug 2012 3:38 AM #21
This technique works for aliases too.
From Brian Moeskau's calendar app, an Event edit window is defined as
ComponentQuery matches the following search correctlyCode:alias : 'widget.extensible.eventeditwindow'
ExtJS version 4.1.1Code:Ext.ComponentQuery.query('window[xtype="extensible.eventeditwindow"]');
-
13 Sep 2012 2:51 AM #22
Sencha where are though?
Sencha where are though?
Sadly there has not been any response from the developers yet...
Here is what they should do/change to make this work:
Ext.ComponentQuery (lines 215ff.)
FROM
TOCode:// Matches a token with possibly (true|false) appended for the "shallow" parameter tokenRe = /^(#)?([\w\-]+|\*)(?:\((true|false)\))?/, matchers = [{ // Checks for .xtype with possibly (true|false) appended for the "shallow" parameter re: /^\.([\w\-]+)(?:\((true|false)\))?/, method: filterByXType },{
Mind the "\." inside the two regular expressions.Code:// Matches a token with possibly (true|false) appended for the "shallow" parameter tokenRe = /^(#)?([\w\-\.]+|\*)(?:\((true|false)\))?/, matchers = [{ // Checks for .xtype with possibly (true|false) appended for the "shallow" parameter re: /^\.([\w\-\.]+)(?:\((true|false)\))?/, method: filterByXType },{
It is really only a small change and has no side effects, as far as we noticed in our application.
Please Sencha, make this happen!
-
23 Jan 2013 9:48 AM #23
Still suffering from this bug.
Is there any news on this issue so far?
-
23 Jan 2013 10:23 AM #24
Backing up GustavR on this one. It would be a very useful fix/improvement.
Overriding is ok, but it's always better if it's actually done by the framework
-
29 Jan 2013 4:42 AM #25
I think if we don't see a bug number on the top of the thread, Sencha is not going to do anything about it.
-
21 Feb 2013 11:30 AM #26
This is still an issue with 4.2.0 Beta 2.
The class manager recognizes the dot fine and allows an xtype of 'myapp.mytextfld' but the ComponentQuery returns nothing when looking via xtype. But the ComponentQuery will return any xtype that extends the base xtype so a search for 'textfield' shows the component of 'myapp.mytextfld'.
If the Class Manager recognizes it as a component the Component Query should return the component based off that xtype with a dot in it.
Dashes work fine with the xtype and Component Query. But now my company has to change its standards for xtypes to not have a dot in it if they want to use the Component Query.
Every xtype we had in 3.x had a dot in it.
You found a bug! We've classified it as
a bug in our system.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
Similar Threads
-
Ext.ComponentQuery.query() not working
By ashish01 in forum Sencha Touch 1.x: DiscussionReplies: 3Last Post: 7 Sep 2012, 4:45 AM -
[OPEN-1062] Load Record by itemId doesn't work for composite fields
By zefciu in forum Ext 3.x: BugsReplies: 1Last Post: 24 Jul 2012, 12:57 PM -
Ext.ComponentQuery.query() only creates an empty array
By Reggae in forum Ext: DiscussionReplies: 5Last Post: 24 May 2011, 4:09 AM -
[OPEN-EXTJSIV-1804]Ext.ComponentQuery xtype
By rchloupe in forum Ext:BugsReplies: 0Last Post: 30 Apr 2011, 12:00 PM -
[OPEN-759] Ext.ComponentQuery.query() Epic Fail!
By gcallaghan in forum Sencha Touch 1.x: BugsReplies: 0Last Post: 3 Feb 2011, 5:50 PM


Reply With Quote