Looks like we can't reproduce the issue or there's a problem in the test case provided.
  1. #1
    Sencha User
    Join Date
    Mar 2012
    Posts
    87
    Vote Rating
    3
    esag_dk is on a distinguished road

      0  

    Default StoreAddEvent assertion (3.0.3)

    StoreAddEvent assertion (3.0.3)


    An update from 3.0.1 to 3.0.3 broke my application, because you've added a non-empty-list-assertion in your StoreAddEvent.
    That's my use case: I'm adding elements to my table(s) using getStore().addAll(listOfElements). The number of the elements is unknown. Checking if it's 0 before each add() call seems to be a bad idea for me (but the only workaround for now). Especially because it had worked before.

    I understand your assertion (there should be no StoreAddEvent, if the store remains unchanged). But it should not be our concern, since it's GXT which fires a StoreAddEvent, even though there are no elements.

  2. #2
    Software Architect
    Join Date
    Sep 2007
    Posts
    13,971
    Vote Rating
    132
    sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light sven is a glorious beacon of light

      0  

  3. #3
    Sencha User
    Join Date
    Mar 2012
    Posts
    87
    Vote Rating
    3
    esag_dk is on a distinguished road

      0  

    Default


    Thanks, it really sounds like it's the same bug, so this thread can be closed.

Thread Participants: 1