Search Type: Posts; User: evant

Page 1 of 5 1 2 3 4

Search: Search took 0.21 seconds.

  1. The grid has been configured with disableSelection: true, so it won't react to the mouse events.
  2. I wouldn't really classify this as a bug, it certainly represents a slippery slope for event resolution. Stores in view models have special processing on them to allow them to relay their events via...
  3. Nulling out the indices was the fix I applied, spliceMerge can end up in a scenario where we're adding multiple chunks, it's just cheaper to blow them away than to attempt all the shifting required...
  4. This is already resolved, the current code reads:

    beforeRender: function() {
    var me = this,

    me.listenerScopeFn = function (defaultScope) {
    if (defaultScope...
  5. The API between them is not 100% compatible. You'll need to provide some more context (a fiddle would be ideal).
  6. Thanks for the report! I have opened a bug in our bug tracker.
  7. Replies
    The release you're using is a pre 5.0.0 beta. setTabPosition exists in the 5.0.0/5.0.1 build.

    The reason the tabs disappear is because the header is the title you've created, not the tabs.
  8. This isn't a bug, the itemId needs to be unique within the container hierarchy, from the docs:!/api/Ext.Component-cfg-itemId
  9. Replies
    The store has a groupField, the historic behaviour of this means that grouping also means sorting, so the store is sorted by "Column1". When you check the box, it changes false -> true, so the...
  10. The idProperty isn't relevant. The issue is that you are giving the record an id, which means it's not a phantom. You would have the same issue if you had:

    Ext.define('Foo', {
  11. This isn't a bug. The reason you don't get an add is because the record is given an explicit id, which makes it not a phantom record, so it doesn't need to send an add request.
  12. Replies
    There's no bug here, but I can see why it might be a bit confusing.

    Because the store is grouped, that also means it's sorted. That means the sorting is done via the checked property. So as you...
  13. Because there's no referenceHolder.

    name: 'Fiddle',
    launch: function() {
    Ext.define('MyPanel2', {
    extend: 'Ext.panel.Panel',
  14. In an effort to be more intuitive, we've now removed the need to explicitly declare the idProperty as null. Any generated idField in the parent will be replaced by one in a subclass, for example:

  15. Thanks for the report! I have opened a bug in our bug tracker.
  16. It would be best to use a formula, something like:

    formulas: {
    isAuthorized: function(get) {
    return get('authUser').theMethod();
  17. I'm not able to reproduce it, but I think it may have something to do with this:

    Have you installed this update recently?

    Also see:...
  18. Yes, it's intended, because it's just the same as any other date format, because it's sent to Ext.Date.format. Most of the date formats need to be sent as strings, so there's no "special case".

  19. I think maybe you're misunderstanding the documentation.

    This means that each component in the hierarchy doesn't require a viewmodel, things in the viewmodel may be "inherited" via a parent...
  20. I don't see that in the latest nightly, it logs:

    create 1
    create 2
    destroy 1
    destroy 2
  21. You configured it not to do that:

    pruneRemoved: false
  22. Thanks for the report! I have opened a bug in our bug tracker.
  23. Not sure what the bug is here. The keepExisting flag defaults to false:!/api/Ext.selection.Model-method-select
  24. Also
    1) It manages the store lifecycle, so the store will be destroyed when the view is
    2) Allows you to use data binding statements

    stores: {
    foo: {
    filters: [{
  25. {[]}

    The above isn't a valid JSON response, what is your server actually returning?
Results 1 to 25 of 112
Page 1 of 5 1 2 3 4