Search Type: Posts; User: jasewell

Search: Search took 0.01 seconds.

  1. (edited for spelling and swapped php tags for code tags)
    This did not produce the desired behavior.
  2. Sample code:


    Ext.create('Ext.panel.Panel', {
    title: 'Outer',
    width: 600,
    height: 200,
    layout: 'border',
    renderTo: Ext.getBody(),
    items: [{
  3. Is there a reason that passing a waitMsg config option to your form.submit() action wouldn't work?
  4. I was thinking something like this:


    defaults: {
    listeners: {
    render: function(me) {
    if (me.xtype == 'textfield')
    ...
  5. Nevertheless, friend's point about using all xtypes is valid. I think what's happening is an id collision in your menus, since the id property is generated once and only once, when...
  6. Depending on where you start the process, you may not be able to count on having as many levels of inheritance as you expect. In other words, you should check to see if p.parentNode is truthy before...
  7. Well, in this case n is a stand in for the "index" of the record you want from the store. I'm putting index in quotes because I don't want to get hung up on whether the actual record actually has a...
  8. Well I don't know what your error is, but the following lines:

    p.parentNode.set('checked', !!pChildCheckedCount);
    p.set('checked', !!pChildCheckedCount);
    have no business being in the...
  9. Yeah. Don't use the shorthand array syntax for the grid's columns config item, but treat it as a full fledged config for the header container.

    Ext.create('Ext.grid.Panel', {
    title: 'Important...
  10. The function created by dateRendererer expects a JavaScript Date object as input. That's why your first one is working. The second one looks like it's already in your desired format, so perhaps you...
  11. Are you using index to find the next record in the store? If so, I'd recommend using store.getAt(n) instead. You can count on that continuing to work as you add and remove records.
  12. Short answer: you know how to get to the parent of a node, and you know how to loop across the children of a node. Checking the siblings is as simple as setting a variable to 0 and incrementing it...
  13. What do you mean when you say the index property has been lost? Does the new record not appear in your grid where you expected?
  14. It sounds like you need to check siblings before setting your parent node. You could step through p's children and add up how many of them are checked, then:

    p.set('checked', !!pChildCheckedCount);
  15. Ext.grid.View has a 'refresh' event. You'd add a listener to your grid config like so.


    ...
    viewConfig: {
    listeners: { refresh: function(gridView, eOpt); }
    },
    ...
  16. I hadn't thought of that, thanks!
  17. I think that's an equivalent question, provided we don't count rows you'd have to scroll down to see as "displayed".
  18. I could do something like that, yeah. We make a lot of use of the grouping and groupingsummary features, which would complicate things a bit, but it's still a solvable problem. I hate to do something...
  19. Does Ext.grid.View have an easy way to get an answer to the question "Given the current layout of this grid, how many rows are there room to display?"

    Thanks in advance.
  20. The workaround I eventually settled on is simpler (with all the good and bad that implies) than the other solutions I've seen to this problem on the forums. Simply put: the parent model has an unused...
  21. Aha! Now that's I've looked it over more closely, yes, it works great. I was looking at CellEditing, and didn't notice that you'd set selectOnFocus on the editor. Thank you.
  22. Not really, no.
    Let me restate my issue more succinctly: Calling selectText() on the textfield created by CellEditing to edit a grid cell causes the field to vanish. I don't know if this is a bug, a...
  23. I've got a large grid with a CellEditing plugin and numberfields and textfields. I want to select all the text in a cell when the user clicks or tabs into it, so I extended the CellEditing plugin and...
  24. Replies
    7
    Views
    1,003
    Great!
    I hope it's not belaboring the obvious to point out that the reason collapseFirst didn't do what you needed was that the tool was being added after the panel was created.
  25. Replies
    7
    Views
    1,003
    Try this:

    var x=Ext.getCmp('myPortlet').down(); //panel header
    if (!x.tools.plus){
    x.insert(0, {
    type:'plus',
    handler: function(){
    myFunction();
    }
    },
Results 1 to 25 of 25