Results 1 to 6 of 6

Thread: TreePicker binding problem in 5.1

    Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.
  1. #1
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default TreePicker binding problem in 5.1

    Treepicker has a problem : When you change its value, you cannot see the changes in somewhere else.
    explaining it or providing a sample is a little hard but I could find the source of problem.

    You overrided the setValue function but at last line you returned me. but in main setValue implementation you returned return me.mixins.field.setValue.call(me, value);

    I corrected the code and everything was ok after that. The override solution is :

    Code:
    Ext.define('Ext.ux.TreePicker-BUG', {
        requires: ['Ext.ux.TreePicker'],
        override: 'Ext.ux.TreePicker',
        setValue: function (value) {
            this.callParent([value]);
            return this.mixins.field.setValue.call(this, value);
        }
    });

  2. #2
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    Thanks for the report and override. Can you please post a test case so that our developers can troubleshoot and fix this? Thanks.

  3. #3
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    You can do the following these steps :
    1. Make a cell editing grid with a treepicker column
    2. Make an editor panel which is bound to grid selected row
    3. Bound the grid and both treepickers (one in column and one in panel) to the related data stores.
    4. Try to change the treepicker value in editor panel
    5. You will see that the bound value in related cell (in selected row of grid) is not changed simultaneously.
    sorry for no fiddle! but you can give it to your developers. They will got the point as they see the override.

  4. #4
    Sencha User razvanioan's Avatar
    Join Date
    Feb 2008
    Location
    Romania
    Posts
    135

    Default

    Good one Mahmoud, I confirm the issue & your resolution (on 5.0.1 as well) !

    Thx
    ---
    Razvan Ioan ANASTASESCU
    Senior WEB Developer

  5. #5
    Sencha User
    Join Date
    Apr 2013
    Posts
    137

    Default

    Hey! I have this bug in ExtJs 6.2.1 too!

  6. #6
    Sencha User
    Join Date
    Feb 2013
    Location
    California
    Posts
    11,985

    Default

    I haven't been able to reproduce this issue. Any chance you can post a runnable test case?
    https://fiddle.sencha.com/#view/editor

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
  •