Hey, > Why should that be a problem at all? Overwriting method 'A' doesn't force > anyone to overwrite method 'B' as well! > Those (generated) methods 'setFoo', 'getFoo' (and 'isFoo') are public methods. > You can override any public method! And you should be able to do so with the > generated ones as well! In an abstract matter of course. But those methods are connected together as the setter and the getter need to access the same value e.g.
> I am pretty sure that I've overridden one or two generated accessors/mutuators > myself in my current project and it would be very sad, if that doesn't work in > 3.0 anymore. Overriding one of the generated methods usually breaks all others. If we override the setter, the getter will always return wrong values because the generated setter can not be used anymore. If you want to fix that in your custom setter, you have to access the internal flags used by the property system. Still, you would have to implement all by yourself e.g. the checks, the events and so on. We do have the apply methods for exactly that use case. But the same is true for the getter or any other generated method. They only work together as a combination. So you would have to override every single one to make it work. But if you do so, there is no need for a property anymore. Thats why we think its more error prone to allow that feature which has never there before. Regards, Martin ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
