1. #1
    Sencha User
    Join Date
    Feb 2013
    Posts
    31
    Vote Rating
    0
    batman3000 is on a distinguished road

      0  

    Default checkboxgroup lost the name property?

    checkboxgroup lost the name property?


    Funny thing happened as I upgraded my Architect project from extjs 4.1 to 4.2... all the checkboxgroups lost their name property.

    I checked the docs, and the name property no longer exists for checkboxgroups. However, they still have a getName() method and it still works when you set a name.

    So either it this property was accidentally removed or ext js is moving in a new direction...that I don't understand...again

  2. #2
    Sencha - Ext JS Dev Team evant's Avatar
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    16,995
    Vote Rating
    649
    evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute evant has a reputation beyond repute

      0  

    Default


    In the case of a checkbox group, it doesn't really have any meaning. It just acts as a container and delegates setting the value on the children. As such, the name property doesn't really do anything.
    Evan Trimboli
    Sencha Developer
    Twitter - @evantrimboli
    Don't be afraid of the source code!

  3. #3
    Sencha User
    Join Date
    Feb 2013
    Posts
    31
    Vote Rating
    0
    batman3000 is on a distinguished road

      0  

    Default Architect bug

    Architect bug


    Yeah, well my app used to it. And when Architect upgraded the app to 4.2, it broke the app. The reason was because Architect removed all the name properties from all checkboxgroups.

    This sounds like a bug in architect then. There should be no reason why an upgrade removes properties from your app it thinks you don't need.

    This is called giving your client base unnecessary headaches.

Thread Participants: 1

Tags for this Thread