Results 1 to 6 of 6

Thread: Designer 1.2 breaks compatibility with Designer 1.1.2 on store definition

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Nov 2008
    Location
    Currently Mexico
    Posts
    133

    Exclamation Designer 1.2 breaks compatibility with Designer 1.1.2 on store definition

    Designer version tested:
    • Designer 1.2
    Operating System:
    • OSX 10.7
    Framework:
    • Ext JS 3.4
    Description:
    • All combos and grids "lost" their connection with the stores, or all the stores are "undefined".
    Steps to reproduce the problem:

      • Open a 1.1.2 project.
      • Click "Export project"
      • Run your code. All combos and grids start to fail with "this.store is undefined" error.
    The result that was expected:
    • The project should run as with previous version of Designer.
    The result that occurs instead:
    • The project is broken and I had to downgrade to 1.1.2.
    Possible fix:
    • not provided

  2. #2
    Sencha User aconran's Avatar
    Join Date
    Mar 2007
    Posts
    9,488

    Default

    Could you provide a sample project that we can test and fix this issue with?

    Thanks,
    Aaron Conran
    @aconran

  3. #3
    Sencha User
    Join Date
    Nov 2008
    Location
    Currently Mexico
    Posts
    133

    Default

    Hi.

    I've tried, but my project is a huge and complex project and it's not easy to isolate a sample.
    Can I help you in any other way?

    Cya.

  4. #4

    Join Date
    Sep 2007
    Location
    Manchester, Connecticut, USA
    Posts
    100

    Default

    I was able to reproduce the problem. I had a 1.1.2 designer file that I opened in 1.2. I exported the project and then compared the files to those generated by the 1.1.2 version. The difference is that there is no "new storeXXX();" statement at the bottom of the store .js files (where storeXXX is the name of the store class. I found that I had to place explicit new() calls to all my stores in my onReady() method before I created my viewport object. That way all the stores would get initialized properly.

    --Stewart McGuire

  5. #5
    Sencha User
    Join Date
    Nov 2008
    Location
    Currently Mexico
    Posts
    133

    Default

    Thank you very much Steve!

  6. #6
    Ext JS Premium Member Artistan's Avatar
    Join Date
    Apr 2007
    Location
    MN
    Posts
    144

    Default same issue here, but more details....

    Quote Originally Posted by aconran View Post
    Could you provide a sample project that we can test and fix this issue with?

    Thanks,
    4.0-calls.xds

    Here is an example of the store disconnect. I have created a NEW designer 4.0.x project and using 4.0.5
    The store is not "disconnected" but simply not created or in the store manager.
    I believe it has to do with the stores config on the application not creating the store and then the grid is trying to config the store by id, which requires the store to be loaded into the manager?

    To work around this I added an Ext.create to the application.launch method.

    HTML Code:
        launch: function() {
            Ext.QuickTips.init();
            Ext.create('app.store.PhoneEmployeeSearch');
    
            var cmp1 = Ext.create('app.view.CallReports', {
                renderTo: Ext.getBody()
            });
            cmp1.show();
        }
    http://www.sencha.com/forum/showthre...l=1#post640960

    Updated my to call create in initComponent method on the view that is using the store.
    Attached Files Attached Files
    Last edited by Artistan; 24 Aug 2011 at 8:39 AM. Reason: updated code

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •