>>>If user does something, your code reacts to it and assigns the value to this property. You have a choice of bindevent() to the things user may do, or having an _assign method for this property etc. There are ways to avoid having the code in .refresh() doing any checking.
>>
>>I think I understand what you are saying (although I have not used bindevent() yet). But I am not convinced that having a code in the Refresh() method (the way I did it so far) is going to be a problem in the long run.
>
>In the long run, it would be a problem only if it runs too long, too often :). Test on slow machines.
I used to try to design everything to the lowest common denominator (e.g. slowest computer). And I often ended up having two much code and too much maintenance. And a few customers who still used slow machines didn't really appreciate what I was doing for them.
No more Mr. Nice Guy.
Now I design everything for minimum code maintenance and if someone is having a problem I suggest that they spend some money and buy faster machines. Or add memory. Then they appreciate what I am saying :).
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
