Frank Schönheit - Sun Microsystems Germany wrote, On 10/23/06 13:50: > Hi Malte, > >> ... >> >> I for sure don't want to see some "virtual bool IsUnlimitedTextLen() >> const;". > > Why? That's a much cleaner solution than imposing a magic^W special > semantics on a special value - no matter if "0" or "EDIT_NOLIMIT".
1) There is IMHO a lot of API doing something like that with "0". An Edit with max text len "0" doesn't make much sense, so 0 is fine. 2) w/o a special value, you also must introduce something like "EnableMaxTextLen(bool)", otherwise you can't turn off max text len. 3) For a simple Edit, you even don't need such functionality, because there is no difference between "0" for no limit, or datatype_max_size (string). So for an Edit, it seems to be an UI problem: User might understand "0" or "TRUE", but might be confused from 65535 or 4.xxx.xxx.xxx. But I think this is a theoretical discussion, because nobody will change the implementation (now) ;) Malte. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
