Hi Isomorphic,
I was recently dealing with the problem of validating optionDataSource form 'select' field (simillar to this one http://forums.smartclient.com/showthread.php?t=2465). According to this one the field must be of enum type. You are also giving there the solution of assigning possible values to a valueMap and populating the field with this valueMap. Then the validation processes the valueMap values and checks whether it contains the value provided.
But wouldn't it be easier to handle the same way optionDataSource that is defined with the property 'cacheAllData'?? It should allow SmartClient to have access to all possible values client-side. Why the valueMap code juggling?
I was recently dealing with the problem of validating optionDataSource form 'select' field (simillar to this one http://forums.smartclient.com/showthread.php?t=2465). According to this one the field must be of enum type. You are also giving there the solution of assigning possible values to a valueMap and populating the field with this valueMap. Then the validation processes the valueMap values and checks whether it contains the value provided.
But wouldn't it be easier to handle the same way optionDataSource that is defined with the property 'cacheAllData'?? It should allow SmartClient to have access to all possible values client-side. Why the valueMap code juggling?