Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    PickListProperties.bodyStyleName not picked up

    Hi,
    I am using the 8.1 nightly build and it seems that pickListProperties I set on the formitem are overwritten by Smartclient. This is done in the PickList._applyPickListToItem method. Is this intentional? Or how should I override the bodyStyleName of a formItem with a picklist?

    gr. Martin

    #2
    Hi,
    Bumping up, but this time with a testcase which shows it,
    Added pickListProperties to the SmartClient_Explorer.html#listComboBox example, the bodyStyleName of the pickList is not set at test, see the attached screenshot.

    Code:
    isc.DynamicForm.create({
        width: 500,
        numCols: 4,
        fields : [{
            name: "bugStatus", title: "Bug Status", 
            editorType: "comboBox",
    pickListProperties: {
    bodyStyleName: 'test'
    },
            valueMap : {
                "new" : "New",
                "active" : "Active",
                "revisit" : "Revisit",
                "fixed" : "Fixed",
                "delivered" : "Delivered",
                "resolved" : "Resolved",
                "reopened" : "Reopened"
            }
        },{
            name: "itemName", title: "Item Name", editorType: "comboBox", 
            optionDataSource: "supplyItem", pickListWidth: 250
        }]
    });
    Attached Files

    Comment


      #3
      Hi Martin
      We see the problem and it's on our list to be resolved in the near future (likely next week).
      In the meantime you could workaround this via an override to showPickList that explicitly sets the bodyStyleName on the live pickList instance:
      Code:
      showPickList : function () {
          this.Super("showPickList", arguments);
          if (this.pickList) this.pickList.setBodyStyleName("cellOver");
      }
      Regards
      Isomorphic Software

      Comment


        #4
        Thanks clear!

        gr. Martin

        Comment


          #5
          This should now be resolved in the framework (as of the next nightly build - October 8 or greater)

          Comment

          Working...
          X