Kees Jongenburger wrote: > > But anyhow, an other option would be to only add 'enforce="never"' or > > 'enforce="oncreate"' to the pattern of string. That means that it only > > serves as an indication for the gui-editor. Just as 'guitype="string"' > > always was, I think. > > > > But I don't know what the problem excactly is, that you encounter? > This was for me the first feature / annoyance encountered when using 1.8 > I do find it a good feature. It's actually quite easy to enter "enter" > in a fields when you cut'n paste. > But what annoyed me more was the error message. it's even worse then > "don't panic" since it's completely unclear what the problem is.
Actually there should be quite good error messages available, but 1. Perhaps not for all cases good strings are created yet, and you saw a fall back string. 2. Generic editors still need to be changed to avoid the exception all together. This can be done because it is possible to anticipate these kind failures now. (and e.g. only represent the failed form but with the invalid fields marked). Michiel -- Michiel Meeuwissen mihxil' Peperbus 111 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
