Ext.data.TreeStore

Appends an event handler to this object.

Parameters

• eventName : String

  The name of the event to listen for. May also be an object who's property names are event names. See

• handler : Function

  The method the event invokes.

• scope : Object

  (optional) The scope (this reference) in which the handler function is executed. If omitted, defaults to the object which fired the event.

• options : Object

  (optional) An object containing handler configuration. properties. This may contain any of the following properties:

  • scope : Object
    The scope (this reference) in which the handler function is executed. If omitted, defaults to the object which fired the event.
  • delay : Number
    The number of milliseconds to delay the invocation of the handler after the event fires.
  • single : Boolean
    True to add a handler to handle just the next firing of the event, and then remove itself.
  • buffer : Number
    Causes the handler to be scheduled to run in an Ext.util.DelayedTask delayed by the specified number of milliseconds. If the event fires again within that time, the original handler is not invoked, but the new handler is scheduled in its place.
  • target : Observable
    Only call the handler if the event was fired on the target Observable, not if the event was bubbled up from a child Observable.
  • element : String
    This option is only valid for listeners bound to Components. The name of a Component property which references an element to add a listener to.

    This option is useful during Component construction to add DOM event listeners to elements of Components which will exist only after the Component is rendered. For example, to add a click listener to a Panel's body:

    new Ext.panel.Panel({
        title: 'The title',
        listeners: {
            click: this.handlePanelClick,
            element: 'body'
        }
    });
    

    When added in this way, the options available are the options applicable to Ext.core.Element.addListener

  
  

  Combining Options
  Using the options argument, it is possible to combine different types of listeners:
  
  A delayed, one-time listener.

  myPanel.on('hide', this.handleClick, this, {
  single: true,
  delay: 100
  });

  Attaching multiple handlers in 1 call
  The method also allows for a single argument to be passed which is a config object containing properties which specify multiple events. For example:

  myGridPanel.on({
      cellClick: this.onCellClick,
      mouseover: this.onMouseOver,
      mouseout: this.onMouseOut,
      scope: this // Important. Ensure "this" is correct during handler execution
  });
  

  .

Returns

• void   

Adds listeners to any Observable object (or Element) which are automatically removed when this Component is destroyed.

Parameters

• item : Observable/Element

  The item to which to add a listener/listeners.

• ename : Object/String

  The event name, or an object containing event name properties.

• fn : Function

  Optional. If the ename parameter was an event name, this is the handler function.

• scope : Object

  Optional. If the ename parameter was an event name, this is the scope (this reference) in which the handler function is executed.

• opt : Object

  Optional. If the ename parameter was an event name, this is the addListener options.

Returns

• void   

Starts capture on the specified Observable. All events will be passed to the supplied function with the event name + standard signature of the event before the event is fired. If the supplied function returns false, the event will not fire.

Parameters

• o : Observable

  The Observable to capture events from.

• fn : Function

  The function to call when an event is fired.

• scope : Object

  (optional) The scope (this reference) in which the function is executed. Defaults to the Observable firing the event.

Returns

• void   

Removes all listeners for this object including the managed listeners

Returns

• void   

Removes all managed listeners for this object.

Returns

• void   

Enables events fired by this Observable to bubble up an owner hierarchy by calling this.getBubbleTarget() if present. There is no implementation in the Observable base class.

This is commonly used by Ext.Components to bubble events to owner Containers. See Ext.Component.getBubbleTarget. The default implementation in Ext.Component returns the Component's immediate owner. But if a known target is required, this can be overridden to access the required target more quickly.

Example:

Ext.override(Ext.form.field.Base, {
//  Add functionality to Field's initComponent to enable the change event to bubble
initComponent : Ext.Function.createSequence(Ext.form.field.Base.prototype.initComponent, function() {
    this.enableBubble('change');
}),

//  We know that we want Field's events to bubble directly to the FormPanel.
getBubbleTarget : function() {
    if (!this.formPanel) {
        this.formPanel = this.findParentByType('form');
    }
    return this.formPanel;
}
});

var myForm = new Ext.formPanel({
title: 'User Details',
items: [{
    ...
}],
listeners: {
    change: function() {
        // Title goes red if form has been modified.
        myForm.header.setStyle('color', 'red');
    }
}
});

Parameters

• events : String/Array

  The event name to bubble, or an Array of event names.

Returns

• void   

Fires the specified event with the passed parameters (minus the event name).

An event may be set to bubble up an Observable parent hierarchy (See Ext.Component.getBubbleTarget) by calling enableBubble.

Parameters

• eventName : String

  The name of the event to fire.

• args : Object...

  Variable number of parameters are passed to handlers.

Returns

• Boolean   

  returns false if any of the handlers return false otherwise it returns true.

Returns all Model instances that are either currently a phantom (e.g. have no id), or have an ID but have not yet been saved on this Store (this happens when adding a non-phantom record from another Store into this one)

Returns

• Array   

  The Model instances

Returns the proxy currently attached to this proxy instance

Returns

• Ext.data.proxy.Proxy   

  The Proxy instance

Returns an object describing the current sort state of this Store.

Returns

• Object   

  The sort state of the Store. An object with two properties:

  • field : String

    The name of the field by which the Records are sorted.

  • direction : String

    The sort order, 'ASC' or 'DESC' (case-sensitive).

  See sortInfo for additional details.

Returns all Model instances that have been updated in the Store but not yet synchronized with the Proxy

Returns

• Array   

  The updated Model instances

Checks to see if this object has any listeners for a specified event

Parameters

• eventName : String

  The name of the event to check for

Returns

• Boolean   

  True if the event is being listened for, else false

Performs initialization of this mixin. Component classes using this mixin should call this method during their own initialization.

Returns

• void   

Returns true if the Store is currently performing a load operation

Returns

• Boolean   

  True if the Store is currently loading

Sets observability on the passed class constructor.

This makes any event fired on any instance of the passed class also fire a single event through the class allowing for central handling of events on many instances at once.

Usage:

Ext.util.Observable.observe(Ext.data.Connection);
Ext.data.Connection.on('beforerequest', function(con, options) {
    console.log('Ajax request made to ' + options.url);
});

Parameters

• c : Function

  The class constructor to make observable.

• listeners : Object

  An object containing a series of listeners to add. See addListener.

Returns

• void   

Appends an event handler to this object (shorthand for addListener.)

Parameters

• eventName : String

  The type of event to listen for

• handler : Function

  The method the event invokes

• scope : Object

  (optional) The scope (this reference) in which the handler function is executed. If omitted, defaults to the object which fired the event.

• options : Object

  (optional) An object containing handler configuration.

Returns

• void   

Relays selected events from the specified Observable as if the events were fired by this.

Parameters

• origin : Object

  The Observable whose events this object is to relay.

• events : Array

  Array of event names to relay.

• prefix : Object

Returns

• void   

Removes all added captures from the Observable.

Parameters

• o : Observable

  The Observable to release

Returns

• void   

Removes an event handler.

Parameters

• eventName : String

  The type of event the handler was associated with.

• handler : Function

  The handler to remove. This must be a reference to the function passed into the addListener call.

• scope : Object

  (optional) The scope originally specified for the handler.

Returns

• void   

Removes listeners that were added by the mon method.

Parameters

• item : Observable|Element

  The item from which to remove a listener/listeners.

• ename : Object|String

  The event name, or an object containing event name properties.

• fn : Function

  Optional. If the ename parameter was an event name, this is the handler function.

• scope : Object

  Optional. If the ename parameter was an event name, this is the scope (this reference) in which the handler function is executed.

Returns

• void   

Resume firing events. (see suspendEvents) If events were suspended using the queueSuspended parameter, then all events fired during event suspension will be sent to any listeners now.

Returns

• void   

Sets the Store's Proxy by string, config object or Proxy instance

Parameters

• proxy : String|Object|Ext.data.proxy.Proxy

  The new Proxy, which can be either a type string, a configuration object or an Ext.data.proxy.Proxy instance

Returns

• Ext.data.proxy.Proxy   

  The attached Proxy object

Sorts the data in the Store by one or more of its properties. Example usage:

//sort by a single field
myStore.sort('myField', 'DESC');

//sorting by multiple fields
myStore.sort([
    {
        property : 'age',
        direction: 'ASC'
    },
    {
        property : 'name',
        direction: 'DESC'
    }
]);

Internally, Store converts the passed arguments into an array of Ext.util.Sorter instances, and delegates the actual sorting to its internal Ext.util.MixedCollection.

When passing a single string argument to sort, Store maintains a ASC/DESC toggler per field, so this code:

store.sort('myField');
store.sort('myField');
     

Is equivalent to this code, because Store handles the toggling automatically:

store.sort('myField', 'ASC');
store.sort('myField', 'DESC');

Parameters

• sorters : String|Array

  Either a string name of one of the fields in this Store's configured Model, or an Array of sorter configurations.

• direction : String

  The overall direction to sort the data by. Defaults to "ASC".

• where : Object
• doSort : Object

Returns

• void   

Suspend the firing of all events. (see resumeEvents)

Parameters

• queueSuspended : Boolean

  Pass as true to queue up suspended events to be fired after the resumeEvents call instead of discarding all suspended events;

Returns

• void   

Synchronizes the Store with its Proxy. This asks the Proxy to batch together any new, updated and deleted records in the store, updating the Store's internal representation of the records as each operation completes.

Returns

• void   

Removes an event handler (shorthand for removeListener.)

Parameters

• eventName : String

  The type of event the handler was associated with.

• handler : Function

  The handler to remove. This must be a reference to the function passed into the addListener call.

• scope : Object

  (optional) The scope originally specified for the handler.

Returns

• void