John, >Would it be a good idea to have the setter/getter look at the field type >and if it were an array based field to call the "fieldArray" function >directly? That way everything could run off a common single function.
I had a public discussion about this on the list a while back. My original goal was to emulate the functionality I created in qForms--which was all string related. However, it was pointed out that dealing with arrays has some inherited strengths--such as not having to worry about delimiter issues. So I added the fieldArray(). I think it would be confusing for setValue() to take either a string or array, but have getValue() only return a string--since these are paired getter/setter functions if think they should have similar behaviors. If you like using arrays, stick with fieldArray(). Besides, it will automatically convert a string value into an array if it's been supplied a string instead of an array. -Dan
