Alexander Bochmann <ab@lists.gxis.de> a =E9crit sur 2008-01-11 12:42:00 :

> ...on Thu, Jan 10, 2008 at 10:28:34PM -0800, Thor (Hammer of God) wrote:
>=20
> > it turns out, Outlook is doing nothing close to what I feared.
> > Basically, the second instance sees that another Outlook window is
> > running in the same interactive logon space, and when it starts, it=20
just
> > calls another popup in the previous Outlook space and then terminates
> > itself (that's close enough, anyway). The good news is that there is=20
no
> > "user hopping" or "boundary crossing" here.=20
>=20
> Sounds comparable to what the Windows Explorer does when=20
> it is not expicitly set to run as a separate process (or=20
> started with the /separate switch).
>=20
> Is there some design principle behind this kind of behaviour?
>=20
> Alex.
>=20

At least since Windows 3.0, whenever an application starts, it gets a=20
reference to the previous (if any) instance of the app running on the=20
system. There are many applications that will simply exit with a message=20
saying "Fropboz.exe is already running".

It doesn't answer your question as to WHY the functionality is there, or=20
why the Outlook programmers thought about using it that way, but it's=20
hardly something new.