From: Jacek S. <arn...@gm...> - 2008-08-14 11:26:09
|
> there are 3 places where behaviors could/should be changed: And all three should check I guess... > - ADCH++ should make sure it doesn't send forbidden chars in its INF. During startup probably... > - DC++ should handle bad chars in incoming INFs and either discard theses > INFs or replace bad chars with eg spaces. I think it might actually make more sense to set the name / invalid field to a dummy string like "Invalid value" - that'll do more to convince owners not to put these invalid values there in the first place... > - DWT's window and tab controls obviously don't support new lines, so they > should replace CRs & LFs with eg spaces. Hm, I'm not sure this is dwt's responsibility - it should maybe be noted in the docs, but dwt itself should safely assume that it's only being passed valid strings...at least if it only results in ugly display (not crash)... And poy is right - the escaping mechanism of ADC works on a lower level and has nothing to do with the restrictions placed on the various inf fields. > poy |