Results 1 to 10 of 10

Thread: SA 3.0.0.1119 Touch dataview.lIst grouepd:true not possible

    You found a bug! We've classified it as DSGNR-4704 . We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.
  1. #1
    Touch Premium Member
    Join Date
    Jun 2008
    Location
    Germany, Dortmund
    Posts
    249

    Default SA 3.0.0.1119 Touch dataview.lIst grouepd:true not possible

    I have a list with a binded store.

    Tyring to set grouped: true the editor is telling that i need at least some settings on store like grouper, remotegroup, etc.

    The issue is, that SA seems to reference the wrong store.
    In this case SA is telling in a popup message
    "The store "MyDirectStore" ..."
    but the list is bound to a names store!

    If i go to code setting grouped: true, everything works as expected, but on each save.
    grouped will be removed.

    Current workaround is programmaticall set grouped = true like

    list.setGrouped(true);

    on launch/init.

    Please fix.

    Cheers Holger

  2. #2

    Default

    I can verify that there is a bug that shows the wrong store name in the popup.

    The rest of the behavior seems correct to me, though -- it's checking against the correct store even though the message shows the wrong name. Since you mention trying to get around the validation by modifying code, are you saying that this validation is not working correctly, or should not be performed?
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  3. #3
    Touch Premium Member
    Join Date
    Jun 2008
    Location
    Germany, Dortmund
    Posts
    249

    Default

    Hi Jason,
    the issue is not the wrong store name!

    I can not set the property grouped: true!

    Each time i try this, the popup is shown and the action is rejected.
    The property is currently not enable!

    Inisde the directstore, there is a remote group field!

    Currently i set the list.setGrouped(true); onInit and everything is working OK!

    The bug is inside SA that SA does not check the right mapped store for the needed properties to be allowed to use grouped: true!

    Cheers Holger

  4. #4

    Default

    OK, thanks for clarifying. I'm unable to reproduce that issue; can you provide more information like what framework you're using? Or could you put together a project that demonstrates the bug?
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  5. #5
    Touch Premium Member
    Join Date
    Jun 2008
    Location
    Germany, Dortmund
    Posts
    249

    Default

    Hi Jason,
    SA 3.0.0.119
    Touch Library: http://sc13-live.sencha.com/touch/touch-2.3.0/

    by the way, on starting project i got a lot of error warning
    unsupported sub component type: basicfunction

    At Sencha Con aaron was telling, that you internally also are using SA
    with Touch 2.3 so i need at least a fix or update!




    Store Data
    Code:
    Ext.define('OizTouchMessbeleg.store.Messbeleg', {
        extend: 'Ext.data.Store',
    
    
        requires: [
            'OizTouchMessbeleg.model.Messbeleg'
        ],
    
    
        config: {
            groupField: 'pttxt',
            model: 'OizTouchMessbeleg.model.Messbeleg',
            pageSize: 15,
            storeId: 'Messbeleg',
            sorters: [
                {
                    direction: 'DESC',
                    property: 'idate'
                },
                {
                    direction: 'DESC',
                    property: 'itime'
                }
            ]
        }
    });
    Inside Ext.dataview.List
    trying to set grouped:true pops up message box with error.

    How can i solve the issues concerning
    unsupported sub component type: basicfunction

    what is the reason for that?

    Should i send you the project (as archieve?).

    Cheers Holger

  6. #6

    Default

    Is this perhaps a Touch 2.3.x project?

    Turns out 2.3 had a bug where it wasn't checking against groupField or remoteGroup, so you could only get the validation to pass by adding a grouper function. This bug has been fixed recently; could this be the issue you are running into?

    It was definitely checking against the correct store, however.
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  7. #7

    Default

    Oops, race condition in my response.

    So my guess is that you're seeing that touch 2.3 bug I described, which has already been fixed. To verify that, could you try adding a grouper function to that store and see if the validation passes?

    I'm happy to look at the unsupported sub component type errors if you send your project along.
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  8. #8
    Touch Premium Member
    Join Date
    Jun 2008
    Location
    Germany, Dortmund
    Posts
    249

    Default

    Hi Jason,
    adding grouper fixed the issue inside!

    I just mailed my two projects Ext/Touch to

    '[email protected]'

    Maybe you will find out what is going wrong inside SA3.

    Cheers Holger

  9. #9

    Default

    Thanks! I received the projects and am looking at them now.

    I'll resolve the ticket we opened for the original issue here, as it appears both aspects have been fixed.
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

  10. #10

    Default

    Hmm, are you really still on build 1119? That's a very old build. Do you still see the issues in the current 3.0 beta release? See the sticky post at the top of http://www.sencha.com/forum/forumdis...ct-3.x-Q-amp-A

    I don't see the unspported sub component errors in my local build.
    Jason Johnston
    @lojjic
    Sencha Architect Development Team

Posting Permissions

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