Hi
We're using SmartClient 7.0rc2 and have come across the problem identified here
http://forums.smartclient.com/showpost.php?p=391&postcount=2
We tend to use the addProperties method to build out our classes and then use the create method to create instances.
These instances then end up sharing the same instance the fields array defined on the class with undesired consequences.
The post referenced above suggests that there might be a change that would help with this problem (perhaps the create method could create deep copies of collections found on the prototype). I was wondering if there have been changes to the create or perhaps you could suggest how we should be doing this kind of thing.
We're using SmartClient 7.0rc2 and have come across the problem identified here
http://forums.smartclient.com/showpost.php?p=391&postcount=2
We tend to use the addProperties method to build out our classes and then use the create method to create instances.
Code:
isc.defineClass("AccountListMembers", isc.ListGrid).addProperties({ fields:[ {name:"accountCode", width:'33%'}, {name:"accountDesc", width:'*'}, {name:"accountType", width:'33%', align: 'left'} ] }); var availableAccounts = isc.AccountListMembers.create(); var selectedAccounts = isc.AccountListMembers.create(); isc.HLayout.create({members: [availableAccounts, selectedAccounts]});
The post referenced above suggests that there might be a change that would help with this problem (perhaps the create method could create deep copies of collections found on the prototype). I was wondering if there have been changes to the create or perhaps you could suggest how we should be doing this kind of thing.
Comment