> Hi Benoit,
>
> Benoît Minisini wrote:
> > If CurrentUser, CurrentProject and CurrentSystem are the objects that
> > change,
> > then they should raise the events, not the module where they are
> > declared. Shouldn't they? An event is the way an object tells the world
> > it has changed.
> >
> >
Hi Benoit,
Benoît Minisini wrote:
>
> If CurrentUser, CurrentProject and CurrentSystem are the objects that
> change,
> then they should raise the events, not the module where they are declared.
> Shouldn't they? An event is the way an object tells the world it has
> changed.
>
> If you can'
> I have a module called "env" that "holds" three system wide objects
> (CurrentUser, CurrentProject, CurrentSystem). Lots of forms access and use
> these objects (Login, FMain etc etc).
>
> I am trying to signal an unknown number of listeners when one of these
> objects changes, for example is
I have a module called "env" that "holds" three system wide objects
(CurrentUser, CurrentProject, CurrentSystem). Lots of forms access and use
these objects (Login, FMain etc etc).
I am trying to signal an unknown number of listeners when one of these
objects changes, for example is the user ch