lundi 15 septembre 2014

Ext.selection.Model -> doSingleSelect



  1. Thank you for reporting this bug. We will make it our priority to review this report.







  2. Default Ext.selection.Model -> doSingleSelect



    Ext.selection.Model -> doSingleSelect





    hi team,

    the code seems to got changed:



    Code:



    if (changed) {
    if (view && view.rendered && !suppressEvent && !me.preventFocus) {
    nm = view.getNavigationModel();
    if (nm) {
    nm.setPosition(record, null, null, suppressEvent, true);
    }
    }
    me.maybeFireSelectionChange(!suppressEvent);
    }

    the check for a navigation model assumes that your view has a navigationModel config which assumes that every component that uses a selection model is extending Ext.view.AbstractView where this config is defined. this is definitely not the case, since it is a common practise to extend any kind of components and give them a custom selection model which extends Ext.selection.Model. this will throw a JS error since the config is not defined and the getter method does not exist.

    long story short: a check if the getter is defined before calling it would already resolve this one.


    best regards

    tobi








    Best regards

    Tobias Uhlig

    __________

    S-CIRCLES Social Network Engine













  3. Default









    Code:



    if (changed) {
    if (view && view.rendered && !suppressEvent && !me.preventFocus) {
    if (Ext.isFunction(view.getNavigationModel)) {
    nm = view.getNavigationModel();
    if (nm) {
    nm.setPosition(record, null, null, suppressEvent, true);
    }
    }
    }
    me.maybeFireSelectionChange(!suppressEvent);
    }







    Best regards

    Tobias Uhlig

    __________

    S-CIRCLES Social Network Engine














Ext.selection.Model -> doSingleSelect

Aucun commentaire:

Enregistrer un commentaire