Użytkownik Ed Leafe napisał: > > Please explain what you mean by "validate". If you mean does it meet > the requirements of the UI, then yes, you need to do it there. > However, most controls do that already - you can't assign a boolean to > a spinner, or anything but a string to a textbox >
How I can prevent change current control value? Only when form level method validateField returns False. Of course I can overwrite entire control flushValue method, as well I can abandon using framework at all, but this is not a way I want to follow. > If you mean that a value must meet any other criteria, then that's a > business rule. > > No, I have dropdown list and related radio list that depend each other, none of them is dependent any element of database, except the presentation layer. I think, that form mediation in validating business objects is very god move, but there is not enough flexibility. > You always have a choice. The framework does the default for you; if > you want to do something else, you have to code it yourself. > Agree. But one of its role is to make things simpler. That is why I created custom class with validateFieldHook method that do may job. But unfortunately, I can't use it with ClassDesigner :( BTW, is there a plan to extend framework/CD that way, to accept other classes not as patterns, but as superclasses? -- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
