Hi Sebastian, I understand the problem of performance. So I just have to write my own setter method instead of using the property features. I just wanted to ask, before doing so, because sometimes there is a secret setting to disable such a behaviour.
I have two cases, where I would like to have the possibility to call the apply-Method every time. I'm building a wizard with some pages, using back and ok Buttons to switch between this pages. I like to update the pages everytime the Parameters for these pages are set, since in my opinion this would be the perfect time for do so. In this case I started to call an extra refresh method manually and don't use the apply method at all. The other case is a search window. The user can select some data, and the data is provided with more details from the backend and displayed. When the user selects the same dataset twice, there is no update of the data. I like to call the apply Method everytime, because the user could not understand, that the data is not refreshed and I don't want to force the programmer to call two functions everytime to get the right. At least I would think, it would be a good idea, to have a note in the documentation of the apply-Setting, that the function is only called, when the value has changed. It would save me some time finding out, why it is not called everytime. Maria Am Di, 11.09.2007, 12:28, schrieb Sebastian Werner: > Hi Maria, > > > the most time these repeated calls make no sense. So there is not way to > deactivate the behavior. Please tell me the exact use case where you need > this behavior to differ from the current one. Typical things are reloads > of images or iframes sources. > > Bye. > > > Sebastian > > > > > Maria Siebert schrieb: > >> Hi, >> >> >> I have a problem using properties. I configured a property using the >> apply method. But when setting the same value again, the applying method >> is not called. So I looked at the generated function, at I found out, >> that if the old value and the new one are the same, the function is >> quited with return before the apply method is called. I don't understand >> this behaviour, since sometimes it is really useful to call the apply >> function also if it is the same value and if you don't want to, you can >> also use the comparison of old and new value inside the apply method. >> >> So is there any possibility to deactivate this behaviour of the >> properties? >> >> Maria >> >> >> >> ----------------------------------------------------------------------- >> -- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2005. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> qooxdoo-devel mailing list [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
