Bug on Tab and Grid

Hello Smartclient team

I just started working with smartclient and unfortunately found some bugs straight away. Bit worried seeing this bugs while starting with a framework. I even checked the live examples on the website and it is happening there too.

Bug 1: When I place a grid inside a tabpane 1 and close the tabpane 2, it removes the grid from the tabpane 1.

Bug 2: When I freeze any of the columns in the Grid and then edit the row, the data disappears.

Version used: SmartClient_SC_SNAPSHOT-2010-10-18 Server Version evaluation.

isc.ListGrid.create({
    autoDraw: false,canEdit:true,

    ID:"test",
    fields: [
        {name: "itemName", title: "Item", type: "text"},
        {name: "unitCost", title: "Unit Cost", type: "number"}
    ],
    data: [
        {itemName: "17\" LCD Monitor", unitCost: 330},
        {itemName: "Dr. Grip Pens - Black", unitCost: 4.99}
    ]
});

isc.TabSet.create({
    top:40, width:400, height:250,
    tabs:[
        { title:"Tab1",canClose:true,
          pane:isc.Canvas.create({ autoDraw:false, contents:"Contents of Tab1"} )
        },
        { title:"Tab2",
          pane:   test     
}
    ]
});

Thanks for the clear reports. Both these issues are now resolved.

Overall SmartClient is a mature, established framework with a large user-base and a huge range of functionality.
Please do bear in mind that you’re working with a nightly build here - no shipping release has ever had such a bug.

In most cases we do recommend you work with the nightlies for evaluation - we are confident that we maintain a good baseline of stability as well as reacting quickly to resolve issues that people do encounter in the mainline code path. Any “live” code path like this can of course pick up small regressions as features are added - we work hard to make sure we catch these and rectify them as they come up. We also provide patches against shipped releases if these are ever necessary.

Thank you.
I will download the latest and try it out.

Thanks
Paul.

I downloaded the latest(Nov-5-2010 build) and the problem still remains the same.

It is working with the build from 6-Nov.
Thanks.