Announcement

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

    Error icon not rendered in listgrid

    1. SmartClient Version: v12.0p_2018-09-15/Pro Deployment (built 2018-09-15)
    2. Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
    3. N/A
    4. N/A
    5. N/A
    6. Code follows

    Starting from Showcase example Grids/Data Binding/ ListGrid fields.

    Code:
    isc.ListGrid.create({
        ID: "countryList",
        width:500, height:224, alternateRecordStyles:true,
        fields:[
            {name:"countryCode", title:"Code"},
            {name:"countryName", title:"Country"},
            {name:"independence", title:"Nationhood", type:"date", width:100},
            {name:"population", title:"Population", type:"integer"},
            {name:"gdp", title:"GDP", type:"float"}
        ],
        data: countryData,
    [B]canEdit: true[/B]
    })
    [B]countryList.setFieldError(1, 1, "Error icon appears with message");[/B]
    The code snippet does not display the error icon in "China" cell.
    The screenshot below shows no error icon was rendered.
    Click image for larger version

Name:	NoErrorIcon.png
Views:	169
Size:	27.0 KB
ID:	255340

    The same code when executed on SmartClient Version: v11.0p_2016-08-13/Pro Development Only (built 2016-08-13)
    correctly renders the error icon with the message.

    Click image for larger version

Name:	ErrorIcon.png
Views:	131
Size:	29.9 KB
ID:	255341

    This bug is a major issue.
    Is there a work around for that or will it be fixed in a subsequent release?

    #2
    This exact bug was fixed just a few days ago. Please get the latest patched build, and be sure to do so in the future to avoid unnecessary work (on your part and ours).

    Comment


      #3
      Bug fixed in SmartClient Version: v12.0p_2018-10-04/Pro Deployment (built 2018-10-04)

      I cannot simply take the latest patched build and stick it into production. Each upgrade there are dozen of glitches that need to be fixed before moving the new version to production.
      Now that I have taken this version, the various glitches will need to be retested to ensure that this latest build does not (re)introduce glitches.

      Comment

      Working...
      X