1. #201
    Sencha - Community Support Team Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246
    Vote Rating
    98
    Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of

      0  

    Default


    Yes, 'start' and 'limit' are integer parameters (both PagingStore and PagingToolbar do some math with them).

  2. #202
    Sencha User
    Join Date
    Nov 2008
    Posts
    92
    Vote Rating
    1
    diablo is on a distinguished road

      0  

    Default


    hi Condor,

    I have the following situation. A tab panel that holds 2 grids, one using pagingstore and the other one normal store. When I am accessing functions (i.e. loadRecords() ) for the grid with normal store, the store is a instance of PagingStore, used in the first grid. Is there a way to avoid this? Comes this from that PagingStore extends Store?

    Thanks!

  3. #203
    Sencha - Community Support Team Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246
    Vote Rating
    98
    Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of

      0  

    Default


    Yes, v0.5 creates PagingJsonStore etc. wrong, which in turn affects Ext.data.Store. I still need to create a v.0.5.1 for that...

    If you're in a hurry: the fix is somewhere in this thread.

  4. #204
    Sencha User
    Join Date
    Nov 2008
    Posts
    92
    Vote Rating
    1
    diablo is on a distinguished road

      0  

    Default


    Quote Originally Posted by Condor View Post
    Yes, v0.5 creates PagingJsonStore etc. wrong, which in turn affects Ext.data.Store. I still need to create a v.0.5.1 for that...

    If you're in a hurry: the fix is somewhere in this thread.
    thanks for the quick reply. If you are referring to the solution povided by @3dm with reverting to constructor to v0.4.1 i have tried it but unfortunatly it doesn't work for me.

  5. #205
    Sencha - Community Support Team Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246
    Vote Rating
    98
    Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of

      0  

    Default


    Quote Originally Posted by diablo View Post
    thanks for the quick reply. If you are referring to the solution povided by @3dm with reverting to constructor to v0.4.1 i have tried it but unfortunatly it doesn't work for me.
    Yes, that was the fix I was referring to.

    If that doesn't help you must be having a different problem. Can you post an example?

  6. #206
    Sencha User
    Join Date
    Nov 2008
    Posts
    92
    Vote Rating
    1
    diablo is on a distinguished road

      0  

    Default


    Quote Originally Posted by Condor View Post
    Yes, that was the fix I was referring to.

    If that doesn't help you must be having a different problem. Can you post an example?
    Hi Condor. Sorry for the late response. In my case made more sense to switch the first grid to use also a api store.

  7. #207
    Sencha User walldorff's Avatar
    Join Date
    Mar 2008
    Location
    Antwerp, Belgium
    Posts
    164
    Vote Rating
    2
    walldorff is on a distinguished road

      0  

    Default


    Thank you Condor, for the work and effort put in this great extension. Wish you a successful 2011 !

    Roland
    ExtJS 3.4, WAMP Apache 2.2.17, PHP 5.3.5, MySQL 5.5.8

  8. #208
    Sencha User
    Join Date
    Dec 2010
    Posts
    9
    Vote Rating
    0
    colinm is on a distinguished road

      0  

    Default Freezing in "Loading..." AlertBox after pressing Next in paging store

    Freezing in "Loading..." AlertBox after pressing Next in paging store


    Hello,
    this extension is very nice .... easy to use .. i guess perfect ... but i got the following problem: when i press the next page in the pagingtoolbar, the next values appear correctly still, the Loading AlertBox doesn't disappear and freeze the screen.

    Here is my code, first I define a grid having a tolbar:
    Code:
    	    
    OriginalGridTab = Ext.extend(Ext.grid.GridPanel, {
        bbar   : [], 
        initComponent: function(){
            Ext.apply(this, { });
            OriginalGridTab.superclass.initComponent.apply(this, arguments);
                var ptb= new Ext.ux.PagingToolbar({
    		      pageSize: 10,
    		      store: this.store,
    		      displayInfo: true,
    		      displayMsg: 'Assays displayed {0} - {1} of {2}',
    		      emptyMsg: "No assays to display"
    			  });
    	    this.getBottomToolbar().add(ptb);
    	}
    });
    and here i create it:
    Code:
    	var ds = new Ext.ux.data.PagingArrayStore({
                 fields : keysamples, 
                 data : datasamples , 
                 lastOptions: {params: {start: 0, limit: 10}}
            });
    	var origgrid = new OriginalGridTab({ store : ds, cm : cm, viewConfig: { forceFit:true },loadMask:true});
    as i said, everything is working fine (and if i removed the paging stuff, it works perfectly ... but too slow so i need it) except when i press the next button.
    the debugger gives me the following exception:

    HTML Code:
    Uncaught TypeError: Cannot call method 'child' of undefined
    setLink          Exporter-all.js:157
    EXTUTIL.Event.fire        ext-all-debug.js:310
    EXTUTIL.Observable.fireEvent         ext-all-debug.js:54
    (anonymous function)        PagingStore.js:168
    (anonymous function)ext-base.js:7
    which refers to the line 168 in PagingStore which is the following:
    Code:
      this.fireEvent("load", this, r, options);
    Can anyone help me?
    thx
    colin

  9. #209
    Sencha - Community Support Team Condor's Avatar
    Join Date
    Mar 2007
    Location
    The Netherlands
    Posts
    24,246
    Vote Rating
    98
    Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of Condor has much to be proud of

      0  

    Default


    It says the error is on line: setLink Exporter-all.js:157

    I have no idea what that code is.

  10. #210
    Sencha User
    Join Date
    Dec 2010
    Posts
    9
    Vote Rating
    0
    colinm is on a distinguished road

      0  

    Default


    thanks for the fast reply ...
    indeed, someone tested the Exporter-all.js script (this provides functionality to export grid store to excel like format). Well apparently that script was not working so well and was no longer used ... .but still loaded ...
    i removed it and everything works fine ...
    thx again for your extension and happy new year

    colin

Thread Participants: 106

  1. Animal (3 Posts)
  2. galdaka (2 Posts)
  3. cgi-bin (4 Posts)
  4. tchitani (4 Posts)
  5. tobiu (1 Post)
  6. steffenk (1 Post)
  7. renaudham (1 Post)
  8. markpele (1 Post)
  9. Sesshomurai (1 Post)
  10. teddyjas (5 Posts)
  11. buergi (2 Posts)
  12. Buzzwords (2 Posts)
  13. tomcheng76 (4 Posts)
  14. kveeiv (1 Post)
  15. dhisnotnull (2 Posts)
  16. walldorff (1 Post)
  17. brizardh (2 Posts)
  18. elizard (1 Post)
  19. Remy (1 Post)
  20. renoye (8 Posts)
  21. despay (1 Post)
  22. lwexler (2 Posts)
  23. tomim (1 Post)
  24. Mjollnir26 (1 Post)
  25. allenlako (3 Posts)
  26. Andrea Gioia (1 Post)
  27. wp.joju (1 Post)
  28. genio (2 Posts)
  29. 828 (1 Post)
  30. ljschrenk (4 Posts)
  31. diablo (3 Posts)
  32. blakel (1 Post)
  33. Grolubao (2 Posts)
  34. makiavelli (2 Posts)
  35. elesel (1 Post)
  36. Capt.JackSparrow (2 Posts)
  37. ferryman (3 Posts)
  38. cwford (1 Post)
  39. 3dm (1 Post)
  40. imnilesh (1 Post)
  41. Rotterdam (2 Posts)
  42. nandubochkar (1 Post)
  43. Dustin Graham (1 Post)
  44. Boing (2 Posts)
  45. tdteti_ (8 Posts)
  46. vtulin (2 Posts)
  47. hello (1 Post)
  48. PranKe01 (2 Posts)
  49. jbusuulwa (6 Posts)
  50. cwilson (1 Post)
  51. ronaldploeger (1 Post)
  52. scblue (1 Post)
  53. saadkhan (2 Posts)
  54. subbugv (6 Posts)
  55. p3p3 (1 Post)
  56. computeraholic (1 Post)
  57. calabacita (3 Posts)
  58. aghextjs (1 Post)
  59. Arindam Das (1 Post)
  60. aw_zahid (1 Post)
  61. deister (1 Post)
  62. billprince (1 Post)
  63. amol.gaikwad (2 Posts)
  64. george4rotech (7 Posts)
  65. leonrenkema (1 Post)
  66. mvassau (1 Post)
  67. aDoF96 (2 Posts)
  68. attack11 (3 Posts)
  69. chakrics (1 Post)
  70. thangamalar (3 Posts)
  71. mayurid (1 Post)
  72. Lobo (1 Post)
  73. christian130 (3 Posts)
  74. elbino (3 Posts)
  75. eashwaranp (1 Post)
  76. atul.sachan@capgemini.com (3 Posts)
  77. Joe Kuan (1 Post)
  78. kent78 (4 Posts)
  79. dsk1962 (1 Post)
  80. Woodlander (3 Posts)
  81. msmolyak (1 Post)
  82. mond (4 Posts)
  83. anandhasubha (1 Post)
  84. David Warren (1 Post)
  85. colinm (2 Posts)
  86. sothea (1 Post)
  87. incanus (1 Post)
  88. MarceloCajr (1 Post)
  89. knackwurst (1 Post)
  90. Pattie (1 Post)
  91. parnold3 (1 Post)
  92. StanimirPanchev (1 Post)
  93. palashkumar1010 (1 Post)
  94. ash4aque (3 Posts)
  95. farfar (3 Posts)
  96. PrashanthShetty (1 Post)
  97. brprashanth (2 Posts)
  98. perseusy (3 Posts)
  99. theWalli (1 Post)
  100. hieu79vn (1 Post)
  101. Hisamitsu (1 Post)
  102. hensor (1 Post)
  103. northmh (3 Posts)
  104. parax (1 Post)
  105. PankajG (1 Post)
  106. reedcat (1 Post)