Search Type: Posts; User: skirtle
Search: Search took 0.06 seconds.
26 Mar 2016 3:16 AM
Assuming I have understood your question correctly, you would update the underlying model for that row of the grid and perform any 'submit' based on the models in the grid's store.
You haven't implemented getTargetEl so update will be treating el as the target.
11 Sep 2015 8:14 AM
I would also add that having created several 'query editors' like the one in your picture I don't understand why you would want to use a grid. Features like column sorting, column re-ordering, column...
11 Sep 2015 8:08 AM
Component Column is not an editor. It doesn't have any understanding of fields or how you want to bind them to your models. It performs tasks that are common to all components,...
16 Aug 2015 7:01 PM
I suggest that you also consider using maskRe and stripCharsRe.
4 Aug 2015 4:07 AM
Yes, performance appears better using the deferred render. It's misleading though, if you scroll down the grid immediately after rendering you'll find that most of the injected components aren't...
21 Jul 2015 12:07 AM
To understand why, see:
I don't know whether you tried stepping through in the debugger but it should have...
20 Jul 2015 11:47 PM
All of which reinforces my suspicions that the form is being submitted by standard form submit rather than AJAX.
Use a debug build of ExtJS and step through in the debugger. It should quickly...
20 Jul 2015 10:22 PM
What were your observations for the following?
Based on what you've posted so far I believe the problem is the first of these.
The console notice gives the line in ExtJS that makes the...
If you stop propagation then the focus moves to the trigger in the property grid. The problem is you then can't tab to the next field.
You might be able to get that to work with a keydown handler...
17 Jul 2015 6:40 PM
Is the form being submitted via AJAX? The browser debug tools should tell you that. (e.g. in Chrome there's a 'Type' column in the Network section).
Try removing all the response headers, see if...
text : new Date(),
In this example you're creating the Date object when the class is defined and sharing it via the prototype between...
Couldn't you just disable the combobox instead?
There's an empty store created by the framework with the id ext-empty-store, you could use that if you're trying to avoid creating new stores. See...
7 Jul 2015 1:16 PM
I've already given several pointers and suggestions. Without any feedback on those ideas I'm struggling to add anything new.
There's only so much we can do to help you if you don't provide a...
6 Jul 2015 3:40 PM
I quite like this approach but I'm not sure it'll be much faster. Rendering 50 comboboxes takes time no matter how you do it.
You also need to consider sizing and destroying the child components,...
By default a tabpanel has deferredRender set to true, so child items aren't rendered until the tab is first clicked. However, the child items are still instantiated, just not rendered. I sometimes...
It's Ext.menu.Item, not Ext.menu.Menu.
27 Jun 2015 8:14 AM
There's a sliding scale here.
Using some simple HTML & CSS with a suitable renderer is the light-weight solution. Done correctly it'll be really fast and there's little risk of serious problems...
var values = combo.getStore().collect(combo.displayField);
Note that collect assumes the values are unique. If that isn't a safe assumption you can use store.each to loop over the records (models)...
I would discourage you from firing events like this. The blur event should only fire in response to the field losing focus, you shouldn't fake it just to call a listener.
I don't believe firing...
25 Jun 2015 2:37 AM
To get the effect of a button you just need some suitable HTML and CSS. You can use a renderer on the column to churn out whatever mark-up you need.
Wiring up the interactions (hover effects,...
19 Jun 2015 9:36 PM
@kosmonaFFFt. It may be possible but I haven't tried it. My suggestion would be to create a subclass which substitutes the renderer for a summaryRenderer (or creates both, whichever makes sense for...
Probably unrelated but this is not the correct way to extend a class. You should use extend, not overrides. overrides is used for patching existing classes.
No, but it still won't be rendered...
If you include renderTo it will render the component directly to the specified DOM node. This is unnecessary if...
You're rendering a viewport...
OR you're working with a floating component,...
Only the outer-most container should have renderTo - remove it from the button.
Get rid of the Ext.create calls for items, just pass configs with suitable xtypes. What you're doing should work but...
Results 1 to 25 of 120