>Hi John,
>
>Good tip. Though for a situation like this it would be much better to instantiate a global Observer from a design viewpoint.
>
>All forms register to the Observer, and the Click of the button calls the observer to handle the Refreshing of objects. This way the same code would work for all the forms which register.
>
>
What's the difference, in this case? The forms should be (instances or subclassed instances) of the same class, so they could have the same EditState_assign routine, right? So, the code handling this event is stored only once; therefore having an Observer is almost superfluous, _unless_ it's doing some other things too. Now what's the list of good uses for an Observer, and what's the difference if the observing is done by an application object? I think I remember months ago there were some threads here, where several good solutions on form handling (multiple instances of the same form and other issues) were said are handled best by an app object; now it's the Observer (instead or along with it?).

Since the concept of Observer is relatively new, I think we'd need some clarification of the whole idea.