Search Type: Posts; User: n3rd

Page 1 of 3 1 2 3

Search: Search took 0.06 seconds.

  1. It may work with the simplistic code snippet I provided initially, but it doesn't work in our real-life application.

    Thanks for your effort, but don't bother. We're done with Ext JS, we've had too...
  2. Not sure how it happened, but you were right. I've hotlinked for testing purposes, but it still doesn't work.

    me.hasListeners is...
  3. I still doesn't work for us. For some reason the core seems to be an RC still:

    >> Ext.versions
    Object { core=4.1.0rc, extjs=4.1.0}

    Anyway, we'll stick to 4.0.7 for the time being. Other...
  4. This has not been fixed in 4.1, apparently. I do not think we are going to keep using Ext JS in the future.

    Ext version tested:
    Ext 4.1.0-RC2 (broken) Ext 4.0.7 (works)

    Browser versions tested against:
    Chrome 18 IE9 FF11

    DOCTYPE tested against:
  6. You're preaching to the choir :) I never said it was fine the way it is, I just told you what the Sencha guys told me.

    I think their reasoning is this: during development, use ext-all-dev and load...
  7. If I remember correctly, one ExtJS guy told me that the loader was never intended to be used for loading classes dynamically like we do. It was primarily meant to be used during development and...
  8. It seems the same applies to Ext.Function.createDelayed().

    Is there a hotfix available?
  9. A function created with Ext.Function.createBuffered() does not receive the arguments set by the caller.

    var f = Ext.Function.createBuffered(function () {
  10. Replies
    I second that. Please make sure it gets merged back to 4.0.6. Thanks a lot.
  11. Just as a FYI, Evan Trimboli has told me this (in response to this related issue):

    So essentially there is no way to react to (or even be notified of) failed requests caused by the Ext.Loader,...

    Ext version tested:

    Ext 4.0.2

    Browser versions tested against:
  13. No updates on the issue? Some feedback would be appreciated!
  14. I had previously reported this very issue but not gotten any reply which is why I re-posted it in the Premium forum. I sincerely hope I'm having more luck this time.
  15. Bump. This issue is still open.
  16. While that was indeed an error, it had nothing to do with the problem I described. I get the same summary value for the "value" column (where it should be the sum) and the "change %" column (where it...
  17. I'm using an Ext.grid.Panel with the GroupingSummary feature. In a stripped down version of my problem, I've a model with two numeric fields 'value' and 'previous' which (not surprisingly) contain...
  18. Shameless bump. No hints?
  19. In Ext 4.0.0 you could do the following:

    Ext.define('MyModel', {
    extend: '',
    fields: [{
    name: 'id', type: 'integer',
    name: 'name', type: 'string'
  20. I'm using an Ext.grid.Panel with the GroupingSummary feature. In a stripped down version of my problem, I've a model with two numeric fields 'value' and 'previous' which (not surprisingly) contain...
  21. You can use the following hotfix by Evan Trimboli until a new release comes out:

    getTpl: function(name) {
    var me = this,
    prototype =...
  22. Hi all,

    the following code works in FF4 but bombs out in both IE8 ("Object required") and Chrome ("Uncaught TypeError: Cannot read property 'nextSibling' of null"):

    Ext.onReady(function () {...
  23. Personally, I haven't used wildcard-style requires yet, but my guess is that it won't work with any namespace other than Ext for the simple reason that the loader doesn't know anything about what...
  24. That appears to be what I was looking for, thank you! If only it was mentioned in the docs...
  25. I'm trying to migrate a set of components I wrote for Ext 3.3 to 4.0 and I'm having some issues.

    I implemented a drag-n-drop interface based on a (pre-existing) table. The table was a component...
Results 1 to 25 of 60
Page 1 of 3 1 2 3